2021-01-14 01:32:13 +00:00
|
|
|
.TH INXI 1 "2021\-01\-13" 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
|
2018-04-06 22:52:08 +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 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
|
|
|
\fBinxi\fR [\fB\-AbBCdDfFGhiIjJlLmMnNopPrRsSuUVwzZ\fR]
|
2016-10-29 22:25:55 +00:00
|
|
|
|
2020-11-11 23:45:10 +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
|
|
|
|
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
|
|
|
\fBinxi\fR [\fB\-\-memory\-modules\fR] [\fB\-\-memory\-short\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\-\-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
|
|
|
|
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
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBinxi\fR is a command line system information script built for 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
|
|
|
and IRC. It is also used a debugging tool for forum technical support
|
2018-04-06 22:52:08 +00:00
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
\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
|
|
|
|
|
the IRC filter, you can use the \fB\-Z\fR option. This can be useful in debugging
|
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
|
|
|
network connection issues online in a private chat, for example.
|
2018-03-26 22:03:15 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH USING OPTIONS
|
2018-04-06 22:52:08 +00:00
|
|
|
Options can be combined if they do not conflict. You can either group the letters
|
2012-09-15 09:18:08 +00:00
|
|
|
together or separate them.
|
|
|
|
|
|
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
|
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 \-A\fR,\fB \-\-audio\fR
|
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
|
|
|
Show Audio/sound device(s) information, including device driver.
|
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 \-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
|
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 \-B\fR,\fB \-\-battery\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
|
|
|
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,
|
|
|
|
|
\fBdmidecode\fR. \fBdmidecode\fR does not have very much information, and none
|
|
|
|
|
about current battery state/charge/voltage. Supports multiple batteries when
|
|
|
|
|
using \fB/sys\fR data.
|
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
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
Note that for \fBcharge\fR, the output shows the current charge, as well as its
|
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
|
|
|
value as a percentage of the available capacity, which can be less than the original design
|
2018-04-06 22:52:08 +00:00
|
|
|
capacity. In the following example, the actual current available capacity of the battery
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
|
|
|
2018-03-31 03:12:25 +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
|
|
|
|
2018-04-06 22:52:08 +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
|
|
|
|
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
|
|
|
With \fB\-x\fR shows attached \fBDevice\-x\fR information (mouse, keyboard, etc.)
|
|
|
|
|
if they are battery powered.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-c\fR,\fB \-\-color\fR \fR[\fB0\fR\-\fB42\fR]
|
|
|
|
|
Set color scheme. If no scheme number is supplied, 0 is assumed.
|
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
|
|
|
.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 \-c \fR[\fB94\fR\-\fB99\fR]
|
2016-10-29 22:15:43 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
These color selectors run a color selector option prior to inxi starting which lets
|
2012-09-15 09:18:08 +00:00
|
|
|
you set the config file value for the selection.
|
|
|
|
|
|
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
|
|
|
NOTE: All configuration file set color values are removed when output is
|
|
|
|
|
piped or redirected. You must use the explicit runtime \fB\-c <color number>\fR option
|
|
|
|
|
if you want color codes to be present in the piped/redirected output.
|
|
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
Color selectors for each type display (NOTE: IRC and global only show safe color set):
|
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 \-c 94\fR
|
|
|
|
|
\- Console, out of X.
|
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 \-c 95\fR
|
|
|
|
|
\- Terminal, running in X \- like xTerm.
|
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 \-c 96\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- GUI IRC, running in X \- like XChat, Quassel,
|
2012-09-15 09:18:08 +00:00
|
|
|
Konversation 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
|
2017-06-09 17:14:28 +00:00
|
|
|
.B \-c 97\fR
|
|
|
|
|
\- Console IRC running in X \- like irssi in xTerm.
|
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 \-c 98\fR
|
|
|
|
|
\- Console IRC not in X.
|
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 \-c 99\fR
|
|
|
|
|
\- Global \- Overrides/removes all settings.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
Setting a specific color type removes the global color selection.
|
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 \-C\fR,\fB \-\-cpu\fR
|
|
|
|
|
Show full CPU output, including per CPU clock speed and CPU max speed (if available).
|
2018-04-15 17:07:26 +00:00
|
|
|
If max speed data present, shows \fB(max)\fR in short output formats (\fBinxi\fR,
|
|
|
|
|
\fBinxi \-b\fR) if actual CPU speed matches max CPU speed. If max CPU speed does
|
2018-04-06 22:52:08 +00:00
|
|
|
not match actual CPU speed, shows both actual and max speed information.
|
|
|
|
|
See \fB\-x\fR for more options.
|
2018-03-31 03:12:25 +00:00
|
|
|
|
|
|
|
|
For certain CPUs (some ARM, and AMD Zen family) shows CPU die count.
|
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
|
|
|
The details for each CPU include a technical description e.g. \fBtype: MT MCP\fR
|
2017-12-07 19:22:59 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
* \fBMT\fR \- Multi/Hyper Threaded CPU, more than 1 thread per core (previously \fBHT\fR).
|
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
|
|
|
|
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 \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 \fBbase/boost:\fR speed data.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-d\fR,\fB \-\-disk\-full\fR,\fB\-\-optical\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
Show optical drive data as well as \fB\-D\fR hard drive data. With \fB\-x\fR, adds a
|
2018-04-06 22:52:08 +00:00
|
|
|
feature line to the output. Also shows floppy disks if present. Note that there is
|
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
|
|
|
no current way to get any information about the floppy device that we are aware of,
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
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 \-D\fR,\fB \-\-disk\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
|
|
|
Show Hard Disk info. Shows total disk space and used percentage. The disk used
|
|
|
|
|
percentage includes space used by swap partition(s), since those are not usable
|
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
|
|
|
for data storage. Also, unmounted partitions are not counted in disk use percentages
|
|
|
|
|
since inxi has no access to the used amount.
|
|
|
|
|
|
|
|
|
|
If the system has RAID or other logical storage, and if inxi can determine
|
|
|
|
|
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):
|
|
|
|
|
|
|
|
|
|
\fBLocal Storage: total: raw: 5.49 TiB usable: 2.80 TiB used: 1.35 TiB (48.3%)\fR
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
Also shows per disk information: Disk ID, type (if present), vendor (if detected),
|
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
|
|
|
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
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-filter\fR,\fB \-\-filter\-override\fR \- See \fB\-z\fR, \fB\-Z\fR.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-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 \-\-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.
|
|
|
|
|
|
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 \-f\fR,\fB \-\-flags\fR
|
2018-03-31 03:12:25 +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
|
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 \-F\fR,\fB \-\-full\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Show Full output for inxi. Includes all Upper Case line letters except \fB\-W\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
|
|
|
plus \fB\-\-swap\fR, \fB\-s\fR and \fB\-n\fR. Does not show extra verbose options such as
|
2018-04-06 22:52:08 +00:00
|
|
|
\fB\-d \-f \-i \-l \-m \-o \-p \-r \-t \-u \-x\fR unless you use those arguments in
|
2018-03-31 03:12:25 +00:00
|
|
|
the command, e.g.: \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
|
|
|
|
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 \-G\fR,\fB \-\-graphics\fR
|
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
|
|
|
Show Graphic device(s) information, including details of device and display drivers
|
|
|
|
|
(\fBloaded:\fR, and, if applicable: \fBunloaded:\fR, \fBfailed:\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
|
|
|
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
|
|
|
|
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
|
|
|
\fBDisplay: x11 server: Xorg 1.15.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
|
|
|
|
|
|
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
|
|
|
Also shows screen resolution(s) (per monitor/X screen), OpenGL renderer,
|
|
|
|
|
OpenGL core profile version/OpenGL version.
|
|
|
|
|
|
|
|
|
|
Compositor information will show if detected using \fB\-xx\fR option
|
|
|
|
|
or always if detected and Wayland.
|
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
|
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 \-h\fR,\fB \-\-help\fR
|
2018-04-06 22:52:08 +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
|
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
|
|
|
use \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
|
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 \-i\fR,\fB \-\-ip\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 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
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
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 \-I\fR,\fB \-\-info\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Show Information: processes, uptime, memory, IRC client (or shell type if run in
|
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
|
|
|
shell, not IRC), inxi version. See \fB\-Ix\fR, \fB\-Ixx\fR, and \fB\-Ia\fR
|
|
|
|
|
for extra information (init type/version, runlevel, 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
|
|
|
|
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
|
|
|
Note: if \fB\-m\fR is used or triggered, the memory item will show in the main
|
|
|
|
|
Memory: report of \fB\-m\fR, not in \fB\Info:\fR.
|
|
|
|
|
|
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
|
|
|
Rasberry Pi only: uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount,
|
|
|
|
|
if user is in video group and \fBvcgencmd\fR is installed. Uses
|
|
|
|
|
this result to increase the \fBMemory:\fR amount and \fBused:\fR amounts.
|
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.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-J\fR,\fB \-\-usb\fR
|
|
|
|
|
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).
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
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).
|
|
|
|
|
|
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
|
|
|
|
|
\fB3.1\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 \-l\fR,\fB \-\-label\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Show partition labels. Default: main partitions \fB\-P\fR. For full \fB\-p\fR output,
|
2018-03-31 03:12:25 +00:00
|
|
|
use: \fB\-pl\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
|
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
|
|
|
Show Logical volume information, for LVM, LUKS, bcache, etc. Shows
|
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, 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 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.
|
|
|
|
|
|
|
|
|
|
If \fB\-R\fR is used with \fB\-Lxx\fR, \fB\-Lxx\fR will not show RAID
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
\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.
|
|
|
|
|
|
|
|
|
|
\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.
|
|
|
|
|
|
|
|
|
|
Sample:
|
|
|
|
|
|
|
|
|
|
\fBDevice\-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
|
|
|
|
|
|
|
|
|
|
.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
|
|
|
\fBLV\-5: lvm_raid1 type: raid1 dm: dm\-16 size: 4.88 GiB
|
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
|
|
|
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
|
|
|
|
|
.fi
|
|
|
|
|
|
|
|
|
|
It is easier to follow the flow of components and devices using \fB\-y1\fR. In
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
.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
|
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 \-m\fR,\fB \-\-memory\fR
|
2018-04-06 22:52:08 +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
|
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
|
|
|
information. Devices shows locator data (highly variable in syntax), size, speed,
|
2018-04-06 22:52:08 +00:00
|
|
|
type (eg: \fBtype: DDR3\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
|
|
|
|
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
|
|
|
Note: \fB\-m\fR uses \fBdmidecode\fR, which must be run as root (or start
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBinxi\fR with \fBsudo\fR), unless you figure out how to set up sudo to permit
|
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
|
|
|
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.
|
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
|
|
|
|
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
|
|
|
Note: If \fB\-m\fR is triggered RAM total/used report will appear in this section,
|
|
|
|
|
not in \fB\-I\fR or \fB\-tm\fR 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 \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
|
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
|
|
|
can do to get truly reliable data about the system RAM; maybe one day the kernel devs
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
|
|
|
|
is what the actual speed is now. To handle this, if speed and configured speed values
|
|
|
|
|
are different, you will see this instead:
|
|
|
|
|
|
|
|
|
|
\fBspeed: spec: [specified speed] MT/S actual: [actual] MT/S\fR
|
|
|
|
|
|
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
|
|
|
Also, if DDR, and speed in MHz, will change to: \fBspeed: [speed] MT/S ([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:
|
|
|
|
|
RAM: total: 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
|
|
|
|
|
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)
|
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
|
|
|
actual: 61910 MT/s (30955 MHz) note: check
|
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
|
|
|
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)
|
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
|
|
|
actual: 2 MT/s (1 MHz) note: check\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
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
|
|
|
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, 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
|
|
|
|
|
.B \-\-memory\-modules\fR
|
|
|
|
|
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
|
|
|
|
|
.B \-\-memory\-short\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
|
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 \-M\fR,\fB \-\-machine\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 machine data. Device, Motherboard, BIOS, and if present, System Builder (Like Lenovo).
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
2018-03-31 03:12:25 +00:00
|
|
|
latter being legacy BIOS boot mode in a system board using UEFI.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
Device information requires either \fB/sys\fR or \fBdmidecode\fR. Note that 'other\-vm?'
|
|
|
|
|
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,
|
2018-03-31 03:12:25 +00:00
|
|
|
post an issue and we'll get it fixed if possible.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
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 \-n\fR,\fB \-\-network\-advanced\fR
|
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
|
|
|
Show Advanced Network device information in addition to that produced by \fB\-N\fR.
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
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 \-N\fR,\fB \-\-network\fR
|
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
|
|
|
Show Network device(s) information, including device driver. With \fB\-x\fR, shows PCI BusID,
|
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
|
|
|
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
|
|
|
|
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 \-o\fR,\fB \-\-unmounted\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
Show unmounted partition information (includes UUID and LABEL if available).
|
2018-03-31 03:12:25 +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
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
|
|
|
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
|
|
|
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
|
|
|
|
2012-09-15 09:18:08 +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 \-p\fR,\fB \-\-partitions\-full\fR
|
2018-03-31 03:12:25 +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
|
|
|
|
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 \-P\fR,\fB \-\-partitions\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
Show basic Partition information.
|
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
|
|
|
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).
|
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
|
|
|
If \fB\-\-swap\fR is not used, shows active swap partitions (never shows file or
|
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
|
|
|
zram type swap).
|
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
|
|
|
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
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-processes\fR \- See \fB\-t\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 \-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)
|
|
|
|
|
|
2018-07-12 22:34:23 +00:00
|
|
|
\fBAPT\fR (Debian, Ubuntu + derived versions, as well as RPM based
|
2020-04-23 03:04:46 +00:00
|
|
|
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)
|
|
|
|
|
|
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
|
|
|
|
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)
|
|
|
|
|
|
2015-02-16 02:33:41 +00:00
|
|
|
\fBSLACKPKG\fR (Slackware + derived versions)
|
2015-02-16 02:17:58 +00:00
|
|
|
|
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
|
|
|
|
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
|
|
|
See \fB\-rx\fR, \fB\-rxx\fR, and \fB\-ra\fR for installed package count information.
|
|
|
|
|
|
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 \-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
|
|
|
|
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
|
|
|
Note: Only md\-raid, ZFS and hardware RAID are currently supported.
|
|
|
|
|
Other software RAID types may be added, if the software
|
2018-04-06 22:52:08 +00:00
|
|
|
RAID actually 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
|
|
|
|
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
|
|
|
The component ID numbers work like this: mdraid: the numerator
|
|
|
|
|
is the actual mdraid component number; ZFS: the numerator is
|
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
|
|
|
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
|
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 \-s\fR,\fB \-\-sensors\fR
|
2018-04-06 22:52:08 +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)
|
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
|
|
|
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.
|
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
|
|
|
|
|
.B \-\-swap\fR \- See \fB\-j\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
|
|
|
.TP
|
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
|
|
|
.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
|
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 \-t\fR,\fB \-\-processes\fR
|
2018-04-19 02:47:09 +00:00
|
|
|
[\fBc\fR|\fBm\fR|\fBcm\fR|\fBmc NUMBER\fR] Show processes. If no arguments, defaults to \fBcm\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 followed by a number, shows that number of processes for each type
|
2018-03-31 03:12:25 +00:00
|
|
|
(default: \fB5\fR; if in IRC, max: \fB5\fR)
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-03-31 03:12:25 +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
|
|
|
|
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
|
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 \-u\fR,\fB \-\-uuid\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Show partition UUIDs. Default: main partitions \fB\-P\fR. For full \fB\-p\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
output, use: \fB\-pu\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 \-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
|
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 \-\-usb\fR \- See \fB\-J\fR
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-V\fR, \fB\-\-version\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
inxi version information. Prints information then exits.
|
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 \-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
|
|
|
|
|
\- Basic verbose, \fB\-S\fR + basic CPU (cores, type, clock speed, and min/max
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
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
|
|
|
\- Adds networking card (\fB\-N\fR), Machine (\fB\-M\fR) data, Battery (\fB\-B\fR)
|
2018-03-31 03:12:25 +00:00
|
|
|
(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
|
|
|
|
|
\- Adds advanced CPU (\fB\-C\fR) and network (\fB\-n\fR) data; triggers \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
|
|
|
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
|
2018-03-31 03:12:25 +00:00
|
|
|
\- Adds partition size/used data (\fB\-P\fR) for (if present):
|
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
|
|
|
\fB/ /home /var/ /boot\fR. Shows full disk 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
|
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 audio card (\fB\-A\fR), memory/RAM (\fB\-m\fR), sensors (\fB\-s\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
|
|
|
partition label (\fB\-l\fR), UUID (\fB\-u\fR), full swap data (\fB\-j\fR),
|
|
|
|
|
and short form of optical drives.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 6
|
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
|
|
|
\- 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.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 7
|
2017-06-09 17:14:28 +00:00
|
|
|
\- Adds network IP data (\fB\-i\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
|
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
|
|
|
\- All system data available. Adds Logical (\fB\-L\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
|
|
|
|
|
.B \-w\fR,\fB \-\-weather\fR
|
2019-05-01 01:26:25 +00:00
|
|
|
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.
|
2018-03-31 03:12:25 +00:00
|
|
|
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
|
|
|
|
|
|
|
|
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! You will be 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.
|
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
|
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
|
|
|
.B \-W\fR, \fB\-\-weather\-location <location_string>\fR
|
|
|
|
|
Get weather/time for an alternate location. Accepts postal/zip code[, country],
|
2018-04-06 22:52:08 +00:00
|
|
|
city,state pair, or latitude,longitude. Note: city/country/state names must 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
|
|
|
contain spaces. Replace spaces with '\fB+\fR' sign. Don't place spaces around
|
2019-02-08 04:52:41 +00:00
|
|
|
any commas. Postal code is not reliable except for North America and maybe the UK.
|
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
|
|
|
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).
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
See \fIhttps://en.wikipedia.org/wiki/ISO_3166\-1_alpha\-2\fR for current 2 letter
|
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
|
|
|
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
|
|
|
|
|
|
|
|
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! Use of automated queries,
|
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
|
|
|
will result in your access being blocked. If you try to work around the ban, you
|
|
|
|
|
will be permanently banned from this service.
|
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
|
|
|
|
|
.B \-\-weather\-source\fR, \fB\-\-ws <unit>\fR
|
2019-05-01 01:29:35 +00:00
|
|
|
[\fB1\-9\fR] Switches weather data source. Possible values are \fB1\-9\fR. \fB1\-4\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
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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
|
2018-05-13 01:13:48 +00:00
|
|
|
.B \-\-weather\-unit <unit>\fR
|
2018-05-21 22:11:04 +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
|
|
|
|
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
|
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
|
|
|
.B \-y\fR,\fB \-\-width [integer]\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
This is an absolute width override which sets the output line width max.
|
|
|
|
|
Overrides \fBCOLS_MAX_IRC\fR / \fBCOLS_MAX_CONSOLE\fR globals, or the
|
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
|
|
|
actual widths of the terminal. \fB80\fR is the minimum width supported.
|
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
|
|
|
\fB\-1\fR removes width limits. 1 switches to a single indented key/value
|
|
|
|
|
pair per line, and removes all long line wrapping (similar to
|
|
|
|
|
\fBdmidecode\fR output).
|
|
|
|
|
|
|
|
|
|
If no integer value is given, sets width to default of 80.
|
|
|
|
|
|
|
|
|
|
Examples: \fBinxi \-Fxx\ \-y 130\fR or \fBinxi \-Fxxy\fR or \fBinxi \-bay1\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 \-z\fR,\fB \-\-filter\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 security filters for IP addresses, serial numbers, MAC,
|
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
|
|
|
location (\fB\-w\fR), and user home directory name. Removes Host:.
|
|
|
|
|
On by default for IRC clients.
|
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 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 \-Z\fR,\fB \-\-filter\-override\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
|
|
|
|
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:
|
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
|
|
|
|
|
|
|
|
|
|
OR
|
|
|
|
|
|
|
|
|
|
\fB\-\-extra 1\fR, \fB\-\-extra 2\fR, \fB\-\-extra 3\fR
|
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
|
|
|
The following details show which lines / items display extra information for each
|
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
|
|
|
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
|
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.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Adds version/port(s)/driver version (if available) for each Audio
|
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
|
|
|
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
|
|
|
|
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 PCI Bus ID/USB ID number of each Audio 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
|
|
|
|
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
|
|
|
|
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
|
|
|
|
|
\- Adds bogomips on CPU (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
|
|
|
|
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
|
|
|
\- Adds \fBboost: [enabled|disabled]\fR if detected, aka \fBturbo\fR. Not all CPUs
|
|
|
|
|
have this feature.
|
|
|
|
|
|
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
|
|
|
|
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 CPU microarchitecture + revision (e.g. Sandy Bridge, K8, ARMv8, P6,
|
2018-04-06 22:52:08 +00:00
|
|
|
etc.). Only shows data if detected. Newer microarchitectures will have
|
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
|
|
|
to be added as they appear, and require the CPU family ID, model ID,
|
|
|
|
|
and stepping.
|
2017-07-29 01:42:17 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
Examples: \fBarch: Sandy Bridge rev: 2\fR, \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
|
|
|
|
|
|
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
|
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 HDD temperature with disk data.
|
|
|
|
|
|
|
|
|
|
Method 1: if you have hddtemp installed, if you are root
|
2018-04-06 22:52:08 +00:00
|
|
|
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/sbin/hddtemp (sample)
|
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
|
|
|
Method 2: systems running Linux kernels ~5.8 and newer may have drive temp data
|
|
|
|
|
available from /sys. If your system has /sys hwmon drive data, the temps
|
|
|
|
|
will come from /sys data for each drive with that data, and will not require
|
|
|
|
|
root or hddtemp!! This method is MUCH faster than using hddtemp!
|
|
|
|
|
|
|
|
|
|
If you see drive temps running as regular user and you did not configure system
|
|
|
|
|
to use sudo hddtemp, then your system supports this feature. Sometimes one type
|
|
|
|
|
of drive will have the /sys temp data, and another won't, it varies widely.
|
|
|
|
|
If no /sys data is found, inxi will try to use hddtemp methods instead
|
|
|
|
|
for that drive.
|
|
|
|
|
|
|
|
|
|
Hint: is /sys sourced, the temps will be to 1 decimal, like 34.8, if hddtemp
|
|
|
|
|
sourced, they will be integers.
|
|
|
|
|
|
|
|
|
|
You can force use of \fBhddtemp\fR for all drives using \fB\-\-hddtemp\fR.
|
|
|
|
|
|
|
|
|
|
\- If free LVM volume group size detected (root required), show \fBlvm-free:\fR
|
|
|
|
|
on Local Storage line. This is how much unused space the VGs contain, that is,
|
|
|
|
|
space not assigned to LVs.
|
|
|
|
|
|
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
|
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.
|
|
|
|
|
|
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 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
|
|
|
|
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 (for single GPU, nvidia driver) screen number that GPU is running on.
|
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 PCI Bus ID/USB ID number of each Graphics card.
|
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 \-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
|
|
|
|
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 runlevel (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.
|
|
|
|
|
|
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 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
|
|
|
|
|
.B \-x \-j\fR, \fB\-x \-\-swap\fR
|
|
|
|
|
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).
|
|
|
|
|
|
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 \-L\fR, \fB\-x \-\-logical\fR
|
|
|
|
|
\- Adds \fBdm: dm-x\fR to VG > LV and other Device types. This can help tracking
|
|
|
|
|
down which device belongs to what.
|
|
|
|
|
|
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
|
|
|
|
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 type in the Device 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
|
|
|
|
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.
|
|
|
|
|
|
2017-06-09 17:14:28 +00:00
|
|
|
\- Adds version/port(s)/driver version (if available) for each Network card;
|
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 PCI Bus ID/USB ID number of each Network card.
|
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 \-x \-o\fR, \fB\-x \-p\fR, \fB\-x \-P\fR
|
|
|
|
|
\- Adds \fBmapper:\fR (the \fB/dev/mapper/\fR partitioni ID)
|
|
|
|
|
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
|
|
|
|
|
|
|
|
\- 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
|
|
|
|
|
\- Adds basic voltages: 12v, 5v, 3.3v, vbat (\fBipmi\fR, \fBlm-sensors\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.
|
|
|
|
|
|
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
|
|
|
\- 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 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
|
|
|
|
|
.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
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Adds vendor:product ID for each Audio 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
|
|
|
|
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. 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 serial number, voltage (if available). Note that \fBvolts\fR shows the
|
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
|
|
|
data (if available) as the voltage now / minimum design voltage.
|
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
|
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
|
|
|
.B \-xx \-C\fR
|
|
|
|
|
\- Adds \fBL1 cache:\fR and \fBL3 cache:\fR if either are available. Requires
|
|
|
|
|
dmidecode and sudo/root.
|
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
|
2017-06-09 17:14:28 +00:00
|
|
|
\- Adds disk 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
|
|
|
|
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
|
|
|
\- Adds disk speed (if available). This is the theoretical top speed of the
|
|
|
|
|
device as reported. This speed may be restricted by system board limits, eg.
|
|
|
|
|
a SATA 3 drive on a SATA 2 board may report SATA 2 speeds, but this is not
|
|
|
|
|
completely consistent, sometimes a SATA 3 device on a SATA 2 board reports
|
|
|
|
|
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
|
|
|
|
|
GT/s * .8 = Gb/s (10 bits required to transfer 8 bits of data).
|
|
|
|
|
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
|
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Adds vendor:product ID of each Graphics card.
|
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 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
|
|
|
\- Adds Xorg compositor, if found (always shows for Wayland 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
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\- For free drivers, adds OpenGL compatibility version number if available.
|
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
|
|
|
For nonfree drivers, the core version and compatibility versions are usually
|
|
|
|
|
the same. Example:
|
2017-06-09 19:39:43 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
\fBv: 3.3 Mesa 11.2.0 compat\-v: 3.0\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
|
|
|
|
|
|
|
|
\- If available, shows \fBalternate:\fR Xorg drivers. This means a driver on
|
|
|
|
|
the default list of drivers Xorg automatically checks for the card, 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 card. 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.
|
|
|
|
|
|
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
|
|
|
\- If available, shows Xorg dpi (\fBs-dpi:\fR) for the active Xorg \fBScreen\fR
|
|
|
|
|
(not physical monitor). Note that the physical monitor dpi and the Xorg
|
|
|
|
|
dpi are not necessarily the same thing, and can vary widely.
|
|
|
|
|
|
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
|
|
|
|
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 system default runlevel, if detected. Supports Systemd/Upstart/SysVinit
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
|
|
|
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
|
|
|
\- Shows \fBPackages:\fR counts by discovered package manager types. In cases where
|
|
|
|
|
only 1 type had results, does not show total after \fBPackages:\fR. Does not
|
|
|
|
|
show installed package managers wtih 0 packages. See \fB\-a\fR for full output.
|
|
|
|
|
Moves to \fBRepos\fR if \fB\-rxx\fR.
|
|
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Adds parent program (or 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.
|
|
|
|
|
|
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 \-xx \-L\fR, \fB\-xx \-\-logical\fR
|
|
|
|
|
\- Adds internal LVM Logical volumes, like raid image and meta data volumes.
|
|
|
|
|
|
|
|
|
|
\- Adds full list of Components, sub\-components, and their physical devices.
|
|
|
|
|
|
|
|
|
|
\- 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
|
|
|
|
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 Part Number (\fBpart\-no:\fR). Useful for ordering new or
|
2018-04-06 22:52:08 +00:00
|
|
|
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,
|
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
|
|
|
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
|
|
|
|
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 single/double bank memory, if data is found. Note, this may not be 100% right
|
2018-04-06 22:52:08 +00:00
|
|
|
all of the time since it depends on the order that data is found in \fBdmidecode\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
|
|
|
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
|
|
|
|
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
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Adds vendor:product ID for each Network card.
|
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, 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
|
|
|
|
|
\- Adds Packages info. See \fB\-Ixx\fR
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
\- 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
|
2018-07-12 22:13:05 +00:00
|
|
|
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
|
|
|
|
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 \-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
|
|
|
|
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).
|
|
|
|
|
Requires sudo/root and \fBdmidecode\fR.
|
|
|
|
|
|
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
|
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
|
|
|
\- Adds disk 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
|
|
|
|
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 disk partition scheme (in most cases), e.g. \fBscheme: GPT\fR. Currently not
|
|
|
|
|
able to detect all schemes, but handles the most common, e.g. \fBGPT\fR or \fBMBR\fR.
|
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 disk rotation speed (in some but not all cases), e.g. \fBrotation: 7200 rpm\fR.
|
|
|
|
|
Only appears if detected (SSD drives do not have rotation speeds, for example). If none
|
|
|
|
|
found, nothing shows. Not all disks report this speed, so even if they are spinnning,
|
|
|
|
|
no 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
|
|
|
|
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.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\- For \fBrunning in:\fR adds \fB(SSH)\fR to parent, if present. SSH detection
|
2018-03-29 03:57:19 +00:00
|
|
|
uses the \fBwho am i\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.
|
|
|
|
|
|
|
|
|
|
\- Adds, if available, USB speed in \fBMbits/s\fR or \fBGbits/s\fR.
|
|
|
|
|
|
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.
|
|
|
|
|
\fBbus width: 64 bit (total: 72 bits)\fR. Note that total / data widths are mixed up
|
2018-04-06 22:52:08 +00:00
|
|
|
sometimes in dmidecode output, so inxi will take the larger value as the total if
|
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
|
|
|
present. If no total width data is found, then inxi will not show that item.
|
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 Type Detail, e.g. \fBdetail: DDR3 (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. 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, memory module voltage. Only some systems will have this
|
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
|
|
|
data 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 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
|
|
|
|
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
|
|
|
|
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
|
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 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
|
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
|
|
|
|
|
(\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
|
|
|
|
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
|
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 \-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
|
2018-09-08 00:03:27 +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
|
|
|
|
|
\- 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.
|
|
|
|
|
|
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
|
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).
|
|
|
|
|
Format is \fBhexadecimal (decimal)\fR if greater than 9, otherwise \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
|
|
|
|
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
|
|
|
|
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 socket type (for motherboard CPU socket, if available). If results doubtful
|
|
|
|
|
will list two socket types and \fBnote: check\fR. Requires 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.
|
|
|
|
|
.nf
|
|
|
|
|
Sample: \fBsocket: 775 (478) note: check\fR
|
|
|
|
|
Sample: \fBsocket: AM4\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
|
|
|
|
\- Adds DMI CPU base and boost/turbo speeds. Requires sudo/root and \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 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.
|
|
|
|
|
|
|
|
|
|
Samples:
|
|
|
|
|
.nf
|
|
|
|
|
CPU not overclocked, with boost, like Ryzen:
|
|
|
|
|
\fBSpeed: 2861 MHz min/max: 1550/3400 MHz boost: enabled base/boost: 3400/3900\fR
|
|
|
|
|
|
|
|
|
|
Overclocked 2900 MHz CPU, with no boost available:
|
|
|
|
|
\fBSpeed: 2900 MHz min/max: 800/2900 MHz base/boost: 3350/3000\fR
|
|
|
|
|
|
|
|
|
|
Overclocked 3000 MHz CPU, with boosted max speed:
|
|
|
|
|
\fBSpeed: 4190 MHz min/max: 1200/3001 MHz base/boost: 3000/4000\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
|
|
|
|
Note that these numbers can be confusing, but basically, the \fBbase\fR
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
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
|
|
|
\- Adds CPU Vulnerabilities (bugs) as known by your current kernel. Lists by
|
|
|
|
|
\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.
|
|
|
|
|
|
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
|
|
|
Using \fBsmartctl\fR (requires sudo/root privileges).
|
|
|
|
|
|
|
|
|
|
\- 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).
|
|
|
|
|
|
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 SMART report line: status, enabled/disabled, health, powered on,
|
2020-04-23 03:04:46 +00:00
|
|
|
cycles, and some error cases if out of range values. Note that for Pre\-fail items,
|
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
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
\- Adds, for USB or other external drives, actual model name/serial if
|
|
|
|
|
available, and different from enclosure model/serial, and corrects block
|
|
|
|
|
sizes if necessary. Adds in drive temperature for some drives as well,
|
|
|
|
|
and other useful data.
|
|
|
|
|
|
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
|
|
|
|
|
Triggers a much more complete Screen/Monitor output on the
|
|
|
|
|
\fBDisplay:\fR line of \fB\-G\fR. Note that the
|
|
|
|
|
basic feature requires \fBxdpyinfo\fR, and the advanced per monitor
|
|
|
|
|
feature requires \fBxrandr\fR.
|
|
|
|
|
|
|
|
|
|
No support currently exists for \fBWayland\fR since we so far can find
|
|
|
|
|
no documentation or easy methods to extract this information from \fBWayland\fR
|
|
|
|
|
compositors. This unfortunate situation may change in the future, hopefully.
|
|
|
|
|
However, most \fBWayland\fR systems also come with \fBxwayland\fR,
|
|
|
|
|
which should supply the tools necessary for the time being.
|
|
|
|
|
|
|
|
|
|
Further note that all references to \fBDisplays\fR, \fBScreens\fR,
|
|
|
|
|
and \fBMonitors\fR are referring to the \fBX\fR technical terms,
|
|
|
|
|
not normal consumer usage. 1 \fBDisplay\fR runs 1 or more
|
|
|
|
|
\fBScreens\fR, and a \fBScreen\fR runs 1 or more \fBMonitors\fR.
|
|
|
|
|
|
|
|
|
|
\- Adds \fBDisplay\fR ID, for the Display running the Screen that runs the Monitors.
|
|
|
|
|
|
|
|
|
|
\- Adds total number of \fBScreens\fR listed for the current \fBDisplay\fR.
|
|
|
|
|
|
|
|
|
|
\- Adds default \fBScreen\fR ID if Screen (not monitor!) total is greater than 1.
|
|
|
|
|
|
|
|
|
|
\- Adds \fBScreen\fR line, which includes the ID (\fBScreen: 0\fR) then \fBs-res\fR
|
2020-04-23 03:04:46 +00:00
|
|
|
(Screen resolution), \fBs\-dpi\fR, \fBs\-size\fR and \fBs\-diag\fR. Remember, this is an
|
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
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
\- Adds \fBMonitor\fR ID(s). Monitors are a subset of a Screen, each of which
|
|
|
|
|
can have one or more monitors. Normally a dual monitor setup is 2 monitors
|
|
|
|
|
run by one Xorg Screen. Each monitor has the following data, if available:
|
|
|
|
|
|
|
|
|
|
\- \fBres:\fR resolution in pixels. This is the individual monitor's
|
|
|
|
|
reported pixel dimensions.
|
|
|
|
|
|
|
|
|
|
\- \fBhz:\fR frequency in Herz, as reported to Xorg. Note that there have been
|
|
|
|
|
and may continue to be bugs with how Xorg treats > 1 monitor frequencies.
|
|
|
|
|
|
|
|
|
|
\- \fBdpi:\fR dpi (dots per inch), aka, ppi (pixels per inch). This is the
|
|
|
|
|
physical screen dpi, which is calculated using the screen dimensions and its
|
|
|
|
|
resolution.
|
|
|
|
|
|
|
|
|
|
\- \fBsize:\fR size in mm (inches). Note that this is the real monitor size,
|
|
|
|
|
not the Xorg Screen size, which can be quite different (1 Xorg Screen can
|
|
|
|
|
for instance contain two or more monitors).
|
|
|
|
|
|
|
|
|
|
\- \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.
|
|
|
|
|
|
|
|
|
|
Sample (with both \fBxdpyinfo\fR and \fBxrandr\fR data available):
|
|
|
|
|
.nf
|
|
|
|
|
\fBinxi \-aG
|
|
|
|
|
Graphics:
|
|
|
|
|
....
|
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
|
|
|
Display: x11 server: X.Org 1.20.6 driver: loaded: modesetting
|
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
|
|
|
display ID: :0.0 screens: 1
|
2020-04-23 03:04:46 +00:00
|
|
|
Screen\-1: 0 s\-res: 2560x1024 s\-dpi: 96 s\-size: 677x271mm (26.7x10.7")
|
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
|
|
|
s\-diag: 729mm (28.7")
|
2020-04-23 03:04:46 +00:00
|
|
|
Monitor\-1: DVI\-I\-0 res: 1280x1024 hz: 60 dpi: 96
|
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
|
|
|
size: 338x270mm (13.3x10.6") diag: 433mm (17")
|
2020-04-23 03:04:46 +00:00
|
|
|
Monitor\-2: VGA\-0 res: 1280x1024 hz: 60 dpi: 86
|
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
|
|
|
size: 376x301mm (14.8x11.9") diag: 482mm (19")
|
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
|
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
|
|
|
\- Adds, if present, possible \fBalternate:\fR kernel modules capable of driving
|
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
|
|
|
each \fBDevice\-x\fR (not including the current \fBloaded:\fR). If no non\-driver
|
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
|
|
|
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
|
|
|
|
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
|
|
|
|
|
Adds Packages, totals, per package manager totals, and number of lib
|
|
|
|
|
packages detected per package manager. Also adds detected package managers
|
|
|
|
|
with 0 packages listed. Moves to \fBRepos\fR if \fB\-ra\fR.
|
|
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBinxi \-aI
|
|
|
|
|
Info:
|
|
|
|
|
....
|
|
|
|
|
Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 5/6/7/8/9
|
|
|
|
|
Packages: apt: 3681 lib: 2096 rpm: 0 Shell: ksh v: A_2020.0.0 default: Bash
|
|
|
|
|
v: 5.0.16 running in: kate inxi: 3.1.04
|
|
|
|
|
.fi
|
|
|
|
|
|
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 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
|
|
|
.B \-a \-j\fR, \fB\-a \-P\fR [swap], \fB\-a \-P\fR [swap]
|
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
|
|
|
\- 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.
|
|
|
|
|
|
|
|
|
|
For \fB\-P\fR per swap physical partition:
|
|
|
|
|
|
|
|
|
|
\fBswappiness: 60 (default) cache pressure: 90 (default 100)\fR
|
|
|
|
|
|
|
|
|
|
For \fB\-j\fR row 1 output:
|
|
|
|
|
|
|
|
|
|
\fBKernel: swappiness: 60 (default) cache pressure: 90 (default 100)\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 device kernel major:minor number (Linux only).
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-a \-L\fR
|
|
|
|
|
\- 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.
|
|
|
|
|
|
|
|
|
|
\- Adds maj-min to LV and other devices.
|
|
|
|
|
|
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
|
|
|
|
|
\- 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.
|
|
|
|
|
|
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
|
|
|
|
|
\- Adds raw partition size, including file system overhead, partition table, e.g.
|
|
|
|
|
|
|
|
|
|
\fBraw size: 60.00 GiB\fR.
|
|
|
|
|
|
|
|
|
|
\- 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
|
|
|
|
|
\- Adds Packages. See \fB\-Ia\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
|
|
|
.TP
|
|
|
|
|
.B \-a \-R\fR
|
|
|
|
|
\- Adds device kernel major:minor number (mdraid, Linux only).
|
|
|
|
|
|
|
|
|
|
\- Adds, if available, component size, major:minor number, state (Linux only).
|
|
|
|
|
Turns Component report to 1 component per line if size and major:minor present.
|
|
|
|
|
|
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
|
|
|
|
|
\- Adds kernel boot parameters to \fBKernel\fR section (if detected). Support
|
|
|
|
|
varies by OS type.
|
|
|
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
Bypass \fBPerl\fR as a downloader option. Priority is: Perl (HTTP::Tiny),
|
2018-04-04 06:41:06 +00:00
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
Bypass \fBCurl\fR as a downloader option. Priority is: Perl (HTTP::Tiny),
|
2018-04-04 06:41:06 +00:00
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
Bypass \fBFetch\fR as a downloader option. Priority is: Perl (HTTP::Tiny),
|
2018-04-04 06:41:06 +00:00
|
|
|
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
|
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
|
|
|
Bypass \fBWget\fR as a downloader option. Priority is: Perl (HTTP::Tiny),
|
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
|
|
|
Curl, Wget, Fetch, OpenBSD only: ftp
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-alt 44\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Bypass \fBCurl\fR, \fBFetch\fR, and \fBWget\fR as downloader options. This
|
|
|
|
|
basically forces the downloader selection to use \fBPerl 5.x\fR \fBHTTP::Tiny\fR,
|
|
|
|
|
which is generally slower than \fBCurl\fR or \fBWget\fR but it may help bypass
|
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
|
|
|
issues with downloading.
|
2017-06-09 02:29:55 +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
|
|
|
|
|
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.
|
|
|
|
|
|
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
|
2018-04-06 22:52:08 +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,
|
2018-04-04 06:41:06 +00:00
|
|
|
or any display you specify.
|
2017-06-10 21:42:49 +00:00
|
|
|
|
2018-04-06 22:52:08 +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
|
|
|
|
|
other free drivers such as nouveau/ATI is currently unknown. It may be that
|
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
|
|
|
this is a bug with the Intel graphics driver \- more information is required.
|
2017-06-10 21:42:49 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
You can test this easily by running the following command out of X/display server:
|
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
|
|
|
\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
|
2018-04-06 22:52:08 +00:00
|
|
|
Force use of \fBdmidecode\fR. This will override \fB/sys\fR data in some lines,
|
2018-04-04 06:41:06 +00:00
|
|
|
e.g. \fB\-M\fR or \fB\-B\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, 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
|
|
|
|
|
Force use of hddtemp instead of /sys temp data for disks.
|
|
|
|
|
|
2018-03-24 09:18:41 +00:00
|
|
|
.TP
|
2018-03-26 22:03:15 +00:00
|
|
|
.B \-\-host\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Turns on hostname in System line. Overrides inxi config file value (if set):
|
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
|
|
|
|
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
|
|
|
\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 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 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
|
|
|
|
|
Temporary override of \fBNO_HTML_WAN\fR configuration item. Only use to test w/wo
|
|
|
|
|
HTML downloaders for WAN IP. Restores default behavior for WAN IP, which is use HTML
|
|
|
|
|
downloader if present and if dig failed.
|
|
|
|
|
|
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 \-\-limit [\-1 \- x]\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Raise or lower max output limit of IP addresses for \fB\-i\fR. \fB\-1\fR removes limit.
|
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
|
|
|
|
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
|
2018-04-06 22:52:08 +00:00
|
|
|
Updates / installs man page with \fB\-U\fR if \fBpinxi\fR or using \fB\-U 3\fR dev branch.
|
2018-03-26 01:42:49 +00:00
|
|
|
(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
|
|
|
|
|
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.
|
|
|
|
|
|
2018-03-24 09:18:41 +00:00
|
|
|
.TP
|
2018-03-26 22:03:15 +00:00
|
|
|
.B \-\-no\-host\fR
|
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
|
|
|
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):
|
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
|
|
|
indent\-min
|
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
|
|
|
\fBSHOW_HOST='true'\fR \- Same as: \fBSHOW_HOST='false'\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
|
|
|
|
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
|
|
|
This is an absolute override, the host will not show no matter what other
|
|
|
|
|
switches you use.
|
2018-03-24 09:18:41 +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
|
|
|
|
|
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.
|
|
|
|
|
Make permanent with \fBNO_HTML_WAN='true'\fR
|
|
|
|
|
|
2018-03-26 01:42:49 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-man\fR
|
2018-03-26 01:48:30 +00:00
|
|
|
Disables man page install with \fB\-U\fR for master and active development branches.
|
2018-03-26 01:42:49 +00:00
|
|
|
(Only active if \fB\-U\fR is is not disabled by maintainers).
|
|
|
|
|
|
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
|
|
|
|
|
Overrides user set \fBSENSOR_FORCE\fR configuration value. Restores default behavior.
|
|
|
|
|
|
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
|
|
|
|
|
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 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 sudo (which requires configuration to setup anyway for these options)
|
|
|
|
|
just use this option, or \fBNO_SUDO\fR configuration item.
|
|
|
|
|
|
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 \-\-output [json|screen|xml]\fR
|
2019-07-16 02:56:44 +00:00
|
|
|
Change data output type. Requires \-\-output\-file if not \fBscreen\fR.
|
2018-04-06 22:52: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
|
|
|
.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 \-\-output\-file [full path to output file|print]\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
The given directory path must exist. The directory path given must exist,
|
|
|
|
|
The \fBprint\fR options prints to stdout.
|
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
|
|
|
Required for non\-screen \fB\-\-output\fR formats (json|xml).
|
2018-04-06 22:52: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
|
|
|
.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.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBfs\fR \- Partition filesystem. Note that sorts will be somewhat random if all
|
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
|
|
|
filesystems are the same.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBid\fR \- Mount point of partition (default).
|
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
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBlabel\fR \- Label of partition. If partitions have no labels,
|
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
|
|
|
sort will be random.
|
|
|
|
|
|
|
|
|
|
\fBpercent\-used\fR - Percentage of partition size used.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBsize\fR \- KiB size of partition.
|
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
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBuuid\fR \- UUID of the partition.
|
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
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
\fBused\fR \- KiB used of partition.
|
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
|
|
|
|
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
|
|
|
|
|
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 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
|
|
|
|
|
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 default.
|
|
|
|
|
|
|
|
|
|
Example: \fBinxi \-sxx \-\-sensors\-exclude k10temp-pci-00c3\fR
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-sensors\-use\fR
|
|
|
|
|
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
|
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
|
|
|
value shown in lm\-sensors sensors output (Linux/lm-sensors only). If you only want
|
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
|
|
|
to exclude one (or more) sensors from the output, use \fB\-\-sensors\-exlude\fR.
|
|
|
|
|
|
|
|
|
|
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
|
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
|
|
|
consequences. Please be aware that this can lead to many undesirable side\-effects,
|
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
|
|
|
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.
|
2021-01-14 01:32:13 +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
|
|
|
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 from another array that
|
|
|
|
|
has inacurate or misleading data.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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).
|
|
|
|
|
Sleep is used to let the system catch up and show a more accurate CPU use. 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 \-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
|
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
|
|
|
Forces internal IRC flag to off. Used in unhandled cases where the program running
|
|
|
|
|
inxi may not be seen as a shell/tty, but it is not an IRC client. 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 color codes in
|
|
|
|
|
the output, use the \fB\-c [color ID]\fR flag.
|
|
|
|
|
|
|
|
|
|
The sign you need to use this is extra numbers before the key/value pairs of the
|
|
|
|
|
output of your program. These are IRC, not TTY, color codes. Please post a github
|
|
|
|
|
issue if you find you need to use \fB\-\-tty\fR (including the full
|
|
|
|
|
\fB\-Ixxx\fR line) so we can figure out how to add your program to the list
|
|
|
|
|
of whitelisted programs.
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
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
|
|
|
|
|
Forces the USB data generator to use \fB/sys\fR as data source
|
|
|
|
|
instead of \fBlsusb\fR.
|
|
|
|
|
|
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
|
|
|
|
|
Forces the USB data generator to use \fBlsusb\fR as data source. Overrides
|
|
|
|
|
\fBUSB_SYS\fR in user configuration file(s).
|
|
|
|
|
|
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.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
The IP address from the URL must be the last item on the last (non\-empty) line
|
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
|
|
|
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
|
|
|
|
|
|
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
|
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
|
|
|
Force \fBSystem\fR item \fBwm\fR to use \fBwmctrl\fR as data source,
|
|
|
|
|
override default \fBps\fR source.
|
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
|
|
|
|
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
|
|
|
.TP
|
|
|
|
|
.B \-\-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 only 2 columns. 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 (90) and user configuration value:
|
|
|
|
|
|
|
|
|
|
\fBWRAP_MAX=85\fR (previously \fBINDENT_MIN\fR)
|
|
|
|
|
|
|
|
|
|
Previously called: \fB\-\-indent\-min\fR.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH DEBUGGING 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
|
|
|
|
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 \-\-dbg 1\fR
|
|
|
|
|
\- Debug downloader failures. Turns off silent/quiet mode for curl, wget, and
|
|
|
|
|
fetch. Shows more downloader action information. Shows some more information
|
|
|
|
|
for Perl downloader.
|
|
|
|
|
|
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 \-\-dbg [2\-xx]\fR
|
|
|
|
|
\- See github \fBinxi-perl/docs/inxi-values.txt\fR for specific specialized debugging
|
|
|
|
|
options. These can vary but tend to not change much, though they are added as
|
|
|
|
|
needed.
|
|
|
|
|
|
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
|
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
|
|
|
\- On screen debugger output. Output varies depending on current needs
|
|
|
|
|
Usually nothing changes.
|
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.
|
|
|
|
|
|
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
|
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
|
|
|
Force debugger to parse \fB/proc\fR directory data when run as root. Normally this is
|
2018-09-28 21:54:00 +00:00
|
|
|
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
|
|
|
|
|
Force PowerPC debugger parsing of /sys as sudo/root.
|
|
|
|
|
|
|
|
|
|
.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
|
|
|
|
|
BitchX, Gaim/Pidgin, ircII, Irssi, Konversation, Kopete, KSirc, KVIrc, Weechat,
|
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
|
|
|
and Xchat. Plus any others that are capable of displaying either built\-in or external
|
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
|
|
|
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]
|
|
|
|
|
|
2018-04-06 22:52:08 +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/
|
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
\fB/etc/inxi.conf\fR contains the default configurations. These can be overridden
|
|
|
|
|
by user configurations found in one of the following locations (inxi will
|
|
|
|
|
store its config file using the following precedence:
|
|
|
|
|
if \fB$XDG_CONFIG_HOME\fR is not empty, it will go there, else if
|
|
|
|
|
\fB$HOME/.conf/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
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fB$XDG_CONFIG_HOME/inxi.conf\fR > \fB$HOME/.conf/inxi.conf\fR >
|
|
|
|
|
\fB$HOME/.inxi/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
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBCOLS_MAX_CONSOLE\fR The max display column width on terminal.
|
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
|
|
|
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
|
|
|
|
|
|
|
|
\fBCOLS_MAX_NO_DISPLAY\fR The max display column width in console, out of GUI desktop.
|
|
|
|
|
|
2018-04-06 22:52:08 +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
|
2018-04-04 06:41:06 +00:00
|
|
|
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.
|
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
|
|
|
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
|
|
|
|
|
|
|
|
\fBFILTER_STRING\fR Default \fB<filter>\fR. Any string you prefer to see instead
|
|
|
|
|
for filtered values.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBLIMIT\fR Overrides default of \fB10\fR IP addresses per IF. This is only of interest
|
2018-04-04 06:41:06 +00:00
|
|
|
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
|
|
|
|
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
|
|
|
\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 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
|
|
|
\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 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
|
|
|
\fBNO_SUDO\fR Set to \fB1\fR or \fBtrue\fR to disable internal use of \fBsudo\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
|
|
|
\fBPARTITION_SORT\fR Overrides default partition output sort. See
|
|
|
|
|
\fB\-\-partition\-sort\fR for options.
|
|
|
|
|
|
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
|
|
|
\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
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBSENSORS_CPU_NO\fR In cases of ambiguous temp1/temp2 (inxi can't figure out which
|
|
|
|
|
is the CPU), forces sensors to use either value 1 or 2 as CPU temperature. See the
|
2018-04-04 06:41:06 +00:00
|
|
|
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
|
|
|
|
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_EXCLUDE\fR Exclude supplied sensor array[s] from sensor output. Override with
|
|
|
|
|
\fB\-\-sensors\-default\fR. See \fB\-\-sensors\-exclude\fR.
|
|
|
|
|
|
|
|
|
|
\fBSENSORS_USE\fR Use only supplied sensor array[s]. Override with
|
|
|
|
|
\fB\-\-sensors\-default\fR. See \fB\-\-sensors\-use\fR.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBSEP2_CONSOLE\fR Replaces default key / value separator of '\fB:\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.
|
|
|
|
|
|
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
|
|
|
\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.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
The IP address from the URL must be the last item on the last (non\-empty) line of
|
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
|
|
|
the URL's page content source code.
|
|
|
|
|
|
|
|
|
|
Same as \fB\-\-wan\-ip\-url [URL]\fR
|
|
|
|
|
|
|
|
|
|
\fBWEATHER_SOURCE\fR Values: [\fB0-9\fR]. Same as \fB\-\-weather\-source\fR. Values
|
2020-04-23 03:04:46 +00:00
|
|
|
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
|
|
|
|
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
|
|
|
\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, 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
|
|
|
\fBWRAP_MAX\fR (previously \fBINDENT_MIN\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\-\-wrap\-max\fR.
|
|
|
|
|
If \fB80\fR or less, wrap will never happen.
|
|
|
|
|
|
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
|
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
|
|
|
It's best to use the \fB\-c [94\-99]\fR color selector tool to set the following values
|
2018-04-06 22:52:08 +00:00
|
|
|
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
|
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
|
|
|
\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
|
|
|
|
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
|
|
|
NOTE: All default and configuration file set color values are removed when output is
|
|
|
|
|
piped or redirected. You must use the explicit \fB\-c <color number>\fR option
|
|
|
|
|
if you want colors to be present in the piped/redirected output (creating a PDF for
|
|
|
|
|
example).
|
|
|
|
|
|
2018-04-06 22:52:08 +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.
|
|
|
|
|
|
2018-04-06 22:52:08 +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
|
|
|
|
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
|
|
|
|
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
|
|
|
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:
|
New version, new tarball:
Changes: updated inxi updaters to use github locations.
I will do this commit once for googlecode, and once for github, after that,
all commits will go only to github.
inxi moves to github, despite my dislike of for profit source repos, and git,
I decided that I just don't have the time or energy to do it right, so I'm going
to use github.
The project is already moved, though I have left inxi up for the time being on
code.google.com/p/inxi until I move the wiki to http://smxi.org
Everything is pretty much the same, the project url is:
https://github.com/smxi/inxi
The direct download link for the gz is:
https://github.com/smxi/inxi/raw/master/inxi.tar.gz
git pull is:
git pull https://github.com/smxi/inxi master
svn checkout url:
https://github.com/smxi/inxi
And that's about it.
2015-08-20 23:32:57 +00:00
|
|
|
.I https://github.com/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
|
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 IRC irc.oftc.net#smxi
|
2018-04-06 22:52:08 +00:00
|
|
|
You can also visit
|
|
|
|
|
.I irc.oftc.net
|
|
|
|
|
\fRchannel:\fI #smxi\fR to post issues.
|
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
|
New version, new tarball:
Changes: updated inxi updaters to use github locations.
I will do this commit once for googlecode, and once for github, after that,
all commits will go only to github.
inxi moves to github, despite my dislike of for profit source repos, and git,
I decided that I just don't have the time or energy to do it right, so I'm going
to use github.
The project is already moved, though I have left inxi up for the time being on
code.google.com/p/inxi until I move the wiki to http://smxi.org
Everything is pretty much the same, the project url is:
https://github.com/smxi/inxi
The direct download link for the gz is:
https://github.com/smxi/inxi/raw/master/inxi.tar.gz
git pull is:
git pull https://github.com/smxi/inxi master
svn checkout url:
https://github.com/smxi/inxi
And that's about it.
2015-08-20 23:32:57 +00:00
|
|
|
.I https://github.com/smxi/inxi
|
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
|
|
|
|
|
|
|
|
.I https://smxi.org/docs/inxi.htm
|
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:
|
2018-04-04 06:41:06 +00:00
|
|
|
Copyright (C) 2005\-2007 Michiel de Boer aka locsmif
|
2012-09-15 09:18:08 +00:00
|
|
|
|
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
|
|
|
inxi version: Copyright (C) 2008\-2021 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
|
New version, new tarball, new man page. Deprecated xiin uploader, which completes the deprecation
of the xiin.py tool, which is going to become obsolete when python 3 fully replaces python 2.
Since the odds of perl being around and stable are far higher than the odds of xiin.py
even working on python 3, I'm getting ahead of the race. Plus Perl is nicer to work with.
And Perl is a lot faster. I mean, a lot. Not slightly.
And it also works on much older systems, and does not have that Python version < 2.6
failure due to changing Python syntax even between sub versions. xiin.py never ran on
Python 2.5 even when it was relatively recent, which is one reason I'm removing all Python
from inxi.
Basically xiin.py worked only on Python 2.6 or 2.7, period.
Oh, and also handled issue #115 by not making -B show -M data.
2017-08-23 23:14:47 +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
|
|
|
|
2018-04-06 22:52:08 +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
|
|
|
|
|
|
2018-04-06 22:52:08 +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
|
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
|
|
|
non\-stop enthusiasm and willingness to provide real\-time testing and debugging
|
2018-04-06 22:52:08 +00:00
|
|
|
of inxi development.
|
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
|
|
|
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
|
|
|
|
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
|
|
|
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.
|
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
|
|
|
All the inxi package maintainers, distro support people, forum moderators,
|
|
|
|
|
and in particular, sys admins with their particular issues, which almost always
|
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
|
|
|
help make inxi better, and any others who contribute ideas, suggestions, and patches.
|
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
|
|
|
Without a wide range of diverse Linux kernel\-based Free Desktop systems to test
|
2018-04-06 22:52:08 +00:00
|
|
|
on, we could never have gotten inxi to be as reliable and solid as it's turning
|
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
|
|
|
out to be.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
And of course, a big thanks to locsmif, who figured out a lot of the core methods,
|
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
|
|
|
logic, and tricks originally used in inxi Gawk/Bash.
|
