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.
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.
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.
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.
The 3.0.13 system base feature had a small bug in the logic that was supposed to
get the version id from codename, the bug made it never work. This is only relevant
for Ubuntu based distros, so if you are on some other base like Debian or Arch, you
can ignore this one, 3.0.13 will work fine.
No other changes, this was mainly for Mint, and other Ubuntu derived distros in
the future.
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.
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.
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.
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.
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.
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.
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.
bad array looping error.
2. for issue #143, added user PATH to static list of paths, this works around distros
that have chosen to abandon the FSH standard, sigh... This adds to number of paths that
have to be checked, but there was no clean way to handle it otherwise.
3. For MATE, added new version source, mate-session, because mate-about was reporting
a non-matching version number for current MATE.
Two enhancements/bug fixes:
1. inxi did not have support for network block devices /dev/nbd0 type syntax in
disks.
2. this caused a slight failure in lsblk output, so I switched to using lsblk -P
to force paired key values, which are then put into an array of hashes.
These both appeared on an ARM server system, but surprisingly, there were no ARM
specific issues at all on that system.
Both issues/enhancements tested and working fine.
Rolls up a few changes from the latest features:
1. For -Dxxx, if root, will use fdisk to try to find partition table scheme (mbr/gpt)
2. For Display: <protocol> server: will try to use loginctl if out of X and using
--display flag to force display data and not root.
This completes more or less the very last minute features added pre 3.0.0 version.
I wanted to get these in because the features were not super useful since they only
worked on a few systems, particulary the scheme:
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.
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.
like --sleep and -t.
Edits to layout and language, removed some legacy options and language from man and
inxi.
Added partition table detections, rough initial stage. Only works on systems with
udev present currently, will be expanded as we find fast tools. Since the systemd
method is literally up to 25x slower than the udev method, it's not being considered
except maybe as a last, last resort, and probably will never be used.
Many small bugs fixed.
Enhancements:
1. in some cases, will detect partition table type (GTP,MBR) either
with or without root. Uses fast method, which is not available on all systems.
2. Added IPMI sensors tools ipmitool and ipmi-sensors to -s for systems that
use IPMI.
3. Finished man page edits and corrections. Thanks Pete.
4. Added doubled word filter for main -NGA lines, only for Card items.
5. Gave more granular uptime output: like: uptime: 23d 5h 34m
Bugs fixed:
1. RAID - both mdraid and zfs bugs corrected. Issue #135
2. EPYC cpu wrong die count corrected, and also added support for the EPYC type.
Issue #135
3. Possible ARM data glitch that made reader fail on a non-existent file.
Man:
Ongoing updates and edits and corrections and cleanup. Slowly but surely.
1. Bug: cause unknown, but crashes on null file sent to reader, but all those files
have been checked. For now added return if file null.
2. Features: with -Ixxx: show Shell: csh (sudo|su|login) status; show
running in: xfce-terminal (SSH)
ssh session active on remote system.
Various help and man cleanups and additions.
Bugs fixed:
1. stray undefined value corrected
2. fixed BSD no pkg server case, now shows correctly that no pkg server files
were found, not that the OS is not supported.
Features:
1. -t c and m headers cleaned up and simplified
2. man page edits.
3. more standarization of key names for fields, some spelling
and upper/lower case corrections.
Bugs fixed:
1. json/xml outputter had a bug in it that made it validate path wrong.
2. -G -xx option: compositor: for gnome-shell had a bug that would make it show
as running when it wasn't, other strings were tripping the match on systems with
gnome-shell installed but not running,
3. Finally fixed bug with manjaro full version distro string, and tweaked output
to show Manjaro Linux instead of given string.
Features added:
1. --no-man - this lets users turn off man installs. Only really useful for -U
from master, since default is off for pinxi and dev 3 branch.
Man page/help updated to add this option.
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.
To get rid of some non-intuitive options, I've changed some of the --alt values
to more obvious argument names; --dmidecode --no-ssl --no-host --host
This makes them easier to remember, hopefully.
Updated help, man pages to cover this change as well.
Added some more lsblk debugger output to try to start building enough information to
really figure out dm/encrypted/lvm and how those are actually handled internally in
the system in terms of partitions, filesystems, etc.
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.
and a small bug for blank files there.
Second, made the --output error message more clear for bad file structure now lists
the 3 requirements: must be full path, must be writeable directory, and must have
a file in it.
Third, another subtle thing, after a lot of research, am trying the MiB GiB format
because it's technically more accurate and less ambiguous than GB, which is used
either to refer to 1000 bite blocks OR to 1024 blocks, depending on the platform etc.
So rather than hope people get it, trying that slightly more wordy format, and maybe
if people wonder what it is.
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-19 release. I'm putting the last issue requests on the last forums,
so assuming no real further bugs found, expect Perl inxi 2.9.01 to hit around
Monday or Tuesday. If any bugs are found, of course, those will be fixed before
release of the new Perl inxi.
Basically, if you want to see if you can find bugs, this is the time to do it, not
AFTER release. I've posted on many forums, and have given the various distros a
chance to help squash the bugs their users might see, some have been fantastic
(AntiX, you were the best by far), others, not so much. Their loss in the latter
case since the purpose of beta testing is to find bugs before, not after, release.
If you want to see the differences in recommends, and dependencies, grab pinxi
development branch here:
wget -O pinxi https://github.com/smxi/inxi/raw/inxi-perl/pinxi
or:
git clone https://github.com/smxi/inxi --branch inxi-perl --single-branch
and run: pinxi --recommends
The main thing I'd strongly urge all maintainers to add, for long term stability
and speed and reliability, is dig, which can be used if present to get very fast,
reliable, WAN IP information.
All of the other recommends are pretty much the same, for graphics, xdpyinfo,
xrandr, and glxinfo. For networking, ip or ifconfig, along with dig. For all usb
related identification, lsusb, unfortunately, I wish I could get rid of that tool,
it's very slow, but I can't. The --recommends output shows the complete set.
Obviously, Bash and Gawk are no longer recommends, nor are the tools like grep,
sed, tr, wc, etc, all those are done with Perl, so any shell plus Perl 5.08 or
newer Perl 5.x is all that's really required, beyond normal system reporting
tools like lspci etc.
For json/xml export, two Perl modules are needed, again, see --recommends
Making sure tarball etc is up to date, so it can be stored in 'tarball's branch.
MAINTAINERS:
Pinxi 2.9.00-xxx-p (inxi-perl branch) is nearing completion of its beta test cycle,
and, barring any new issues or bugs (TEST IT NOW AND REPORT ISSUES NOW!), I expect
to release pinxi 2.9.00 as inxi 2.9.01 shortly after I complete the advanced
RAID feature, which should be this week.
If no real issues appear during the following week after the inxi 2.9.0 release, it
will be moved to inxi 3.0.0, as the first stable Perl inxi release.
There will be a new branch, inxi-legacy, that will have the Gawk->Bash inxi 2.3..56
files for historical purposes only. No further work will be done on inxi 2.3 from
now on.
cpu output issues. Now inxi handles > 8 cores in terms of output filters,
descriptions, correctly noting that it's multithreaded.
Because AMD has entered the Multithreading game, I've changed the trade term:
HT - HyperThreading to MT - MultiThreading to support both Intel and AMD variants.
Updated CPU output filters to also account for these very large core counts.
I believe this commit now adds full support for the new Ryzen series, but I'll have
to see when it comes to other variants that may appear. I've tried to future proof
the MT tests, but I won't know of those are fully functional and accurate until
inxi sees the real data.
Because I don't want to break existing cpu logic, I just added in a rizen switch,
which will just use cpu_core_count value, then trigger HT output.
This fix may or may not work, but the issue poster vanished and has not followed up.
For now I'm keeping this a Ryzen specific adjustment, but it may be safe to extend
it further, that is, if siblings > 1 && siblings = 2 * cores then it's HT.
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.
easier and more predictable to find. Better section headers, all ordering alpha
by subsections.
Fixed some small debugger gatherer oversights as well.
Note that I made the debugger stuff more portable, so I could use it in another
program.
Note that this is the last choice because it's slow, the order has been revised:
1. curl
2. wget
3. fetch
4. Perl 5 HTTP::Tiny
5. OpenBSD ftp
wget has been downgraded due to the recent 1.19-2 bug with wget -O that did
not get resolved quickly, and which should never have been released since
that's a basic wget action, which means they aren't testing gnu wget the way
they should be.
All inxi downloaders can now use this option. However, in my tests it's signicantly
slower to use HTTP::Tiny than curl or wget, so inxi will test for the downloaders
in that order. While -i uses dig as it's primary IP tool, if dig is not installed,
the IP will follow the same downloader priority. -U and -w/-W use downloaders.
Because HTTP::Tiny is optional, and is merely used if wget/curl/fetch are not
installed, I would not consider Perl to be a real dependency yet, just an option, so
I guess for packager maintainers, Perl should be added as a recommends, or a
dependency if you want to fully support the debugger options (Core Modules).
While I'm still not sure which Perl modules I'm going to be using, I'm sticking
for now to Core Modules, the standard, with some experimental exceptions that
would only be used if the user had them present.
Long term the goal is to get rid of as many dependencies as possible, replacing
them were possible with Perl tools, but this is going to take forever, if it
ever happens, so don't hold your breath.
In the future, I expect more and more components that were gawk to be rewritten
to Perl (Core Modules), slowly, however, very slowly.
Updated --recommends to indicate the downloader options more clearly as well.
Added new options for bypassing curl (-! 41), fetch (-! 42) wget (-! 43), or
curl, fetch, and wget (-! 44) to disable all of them. This is in case one of
those is broken or you want to test Perl downloader, mostly.
Also cleaned up debugger output and made debugger portable to other scripts.
ARM data collection in /sys.
Using 'tree' now instead of ls if it is installed for debugger /sys tree listing.
Added to recommends. Updated bluetooth recommends to note it's dev only. That
should fix issue #127
branches, simplified the options. This corresponds to updates on github where
I'm finally bringing the alternate location self updater back into operational
state after a long dormant period.
Also, and this may be of interest to some maintainers, please note, there is
a new branch: master-plain which does NOT have the gz files inxi.1.gz and
inxi.tar.gz
If you want to avoid the big clones, you can use that branch with this command:
git clone https://github.com/smxi/inxi --branch master-plain --single-branch
And that should only track the basic 3 files: inxi inxi.1 and inxi.changelog
This fixes issue #94
explicitly setting Passive => 1 (true) for some systems and firewall
configurations.
This corrects a failure to upload issue I experienced for a test remote
system that had a different firewall configuration than the dev system has.
nvme disk capacity in full disk capacity listing. Adds nvme name/serial/firmware
revision number. The latter is a new -Dxx output option. Note that as far as I could
tell, so far, nvme is the only disk type that has firmware revision data.
Added support for nvme disk temperature as well, that requires the cli tool nvme.
Updated AMD microarchitecture list to be more granular and complete. Added Intel
microarch type. Note that they are releasing a few new microarchitectures soon but I
was not able to find any model numbers for those.
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.
The issue was not so much with xiin.py as with some new values in /sys that would
hang tree traverse, however, in order to remove the python dependency (except for
uploading -xx@ debugger data, until I can figure out how to do it with Perl), I
rewrote the tree traverse tool into Perl, which also makes it a lot faster and
easier to work with.
This issue appeared on kernel 4.11 as far as I can tell, some new values in /sys make
the traverse hang if it tries to read the values, **/parameters/** and **/debug/** seem
to be the main culprits, but inxi doesn't need that data anyway for debugging purposes
so it's just excluded.
in issue #118
The data seems to suggest that using POWER_SUPPLY_VOLTAGE_MIN_DESIGN as the factor will
be right more often than using POWER_SUPPLY_VOLTAGE_NOW.
Also optimized a bit more on the desktop id logic.
the conversion from mA hours to Wh, and had a math glitch too for charge (ma).
Not sure how this went undetected during testing, oh well. I assume that mA h is not
as common internally as Wh or something.
Anyway, it should be fixed.
-o, -p, -l, -u, -P, -S, -G, -N, -A
Now most output should tend to not wrap, though some strings are unpredictable and
will have to be trimmed by adding them to the min size trimmers one by one.
But it's much better than it was.
Note the following changes required to make the wraps more consistent:
-S - the gcc/bits have been made separate, like: bits: 32 gcc: 5.3
-C - the new microarchitecture -x option now is: arch: K7 [for example]
cache wraps to next line with arch. with -f, bmips now shows on same line as
arch/cache
would have caused failure on older systems. Also added Bash version checker.
Most ps aux data is now searched using bash parameter expansion, and several functions
that were in subshells are now printing to globals instead.
as well so you can see which revision of the cpu microarchitecture your cpu has.
Also fixed a few random vm id issues, I found cases where systemd believes it's bochs
but it is actually kvm, so now the systemd data is not fully trusted, but is confirmed.
Will need some updates to bring the family/model ids to fully current, but should show data for most
cpus. Next release will hopefully include latest model/family ids and microarchitecture names.
Note that while /proc/cpuinfo has the family/model id in decimal, the values are actually generally
found as hexadecimal, so inxi translates that interally so we can store the data the way it is presented.
See issue #116 for ongoing additions to this feature.
but Xorg has not started, which means inxi can't get the video driver from Xorg.0.log as with X.
Added in extra data collection from lspci -v to include the driver for graphics card. this is
only used, for now, if the initial Xorg based driver test works.
Note that this may also work for systems that have not yet started X out of X, in console, I'm
not sure about that, but the graphics driver reporting should be improved.
Note that I'm not yet linking the driver to the specific card/device, it's just going to show
in a comma separated list, I couldn't find multi card systems where the card types are different,
like amd gpu with nvidia card, for example.
But this should correct an issue, at least to start, with expanding wayland support for systems
that don't use or have not started the desktop with Xorg/X11 etc.
core profile data being null, which in turn triggered a bash oddity, where if the IFS is
\n for an array, and if the value of one element is '', then bash ignores that and does
not simply set an empty array key as you'd expect. The correction was to change the IFS
to ^, which worked fine for empty array values.
However, since this bug will impact anyone with empty opengl core profile data, I recommend
updating inxi.
Also, added support for two smaller wm, Sawfish and Afterstep.
This is a good source for lists of wm: http://www.xwinman.org/http://www.xwinman.org/others.php
However, that does not show how to ID it, so i have to do it on a case by case, but I'll
add an issue for showing how to get your wm of choice if it's missing to inxi.
long-standing issue where /dev/ram.. data shows in unmounted disks output. This is
now properly filtered out.
Note that the floppy disk output has no information beyond it's /dev id, eg: /dev/fd0
I could find no meaningful data in /sys related to the floppy disk, not the model, etc, so
I'm just showing presence of disk.
wget/fetch/curl. This allows systems with for example out of date certificate stores
to still download without error. Also a legacy system fix where tty size failed to show.
Also cleaned up man page, slightly changed output for compat version to: (compat-v: 3.0)
gfx variable name fixes to make more obvious the logic as well.
Default will get data from display :0, but if you append :[display-number] to -! 40, it will
use that display instead, for example: inxi -! 40:1 would get information from display 1. Note
that most multi-monitor setups use :0 for both monitors, depending on how it's setup.
This will also let users see any desktop information based on xrop -root output, but it will
depend how it works based on how environmental variables have been set. gnome and kde, which use XDG for
primary detection would not work, for example.
used to not work as root in X, but they do now. So I've removed the root tests for graphics
output, and now only rely on the returned data to determine the output when in X. Out of X
behavior remains the same.
Note that at some point I'll have to see if wayland systems have usable reporting tools to get
screen resolution, opengl info, and so on, but that will have to come one step at a time.
-xx option will show OpenGL compatibility version number as well, though that's largely useless
information for most users, thus the -xx. Note that this reverses the default, which previously
showed OpenGL version, which is actually the compatibility version.
This should resolve#105 pull request, though it does it differently, by switching the default
output to what is more relevant, and offering the compatibility version as an optional output item.
Note that much of the glx information will probably change to more neutral terms once wayland support
starts growing, and systems without xwayland etc libraries appear.
Further note that non free drivers showed the OpenGL core profile version numbers all along, so really
this simply corrects misleading output for free drivers.
and compositor support.
This finally implements a first try at mir/wayland detection, along with basic handling of actual
display server type output.
New output for Display Server: Display Server: x11 (X.Org 1.19.0) driver: nvidia
Note that since almost all current Wayland systems will have X.org also installed, for the time
being, the data in the parentheses will be from X.org regardless of what display server is detected running
the actual desktop. Out of the desktop, console, the only thing that will show is x data..
No other data is available to me yet until I get way more debugger data so I can see what information the various
implementations of wayland without x tools actually makes available, my guess is it won't be much.
Also experimental -xx option: -G shows compositor, but only for wayland/mir currently.
I have no idea if this will work at all, but it's worth giving it a try as a rough beginning to
start handling the wide range of wayland compositors being created.
This feature will probably take several versions to get stable.
Also added new debugger data collector data for wayland information, but the pickings are slim, to
put it mildly.
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
Note that this bug is not universal, but I believe this will make inxi more right than wrong
as a general rule. Further note that altitude is NOT actually the altitude of the city/location
requested, in most cases, but rather the altitude of the weather station data assigned to that
location request.
from BIOSTAR. Also fixed a few other sloppy gsub, and fixed a few gensub errors as well.
Since BIOSTAR is a fairly common mobo, I'm surprised I haven't gotten this bug report
before.
This closes issue #102.
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.
graphics driver, so it would not show in output, which causes support issues for users of that specific
driver, like some cases of Intel. Also inxi would always have failed to show it unloaded in cases where
radeon/nouveau were used but it had been loaded by xorg to begin with. So probably worth updating packages
I'd say.
each disk is on its own line always, this makes it easier to read and/or parse.
Also, the lines now wrap nicely for extra data > console width, or -y 80 for example if
you're trying to force most of the data to fit into 80 columns.
handling, and legacy linux. VM id will remain a work in progress, and will probably
require a few fixes for fringe cases. Nice to have would be things like OpenBSD's
vm which is difficult to detect. However, I believe this should handle roughly 99% of
realworld vm id cases, except for some commercial stuff that will require more data.
Now -M shows device type, like desktop, laptop, notebook, server, blade, vm (and tries to get vm type).
vm detection will take more work, for now I'm just going for the main ones used, but it will certainly
miss some because it's hard to detect them in some cases unless you use root features. Also note, in
most cases a container I believe will display as a vm, which is fine for now.
For BSDs, and older linux, there is a dmidecode fallback detection as well.
Basic support added for Budgie desktop detection. This is waiting more data, so the support will be
missing the version information. Go Budgie!!
Added /var/tmp and /var/log and /opt to basic partition data: -P
This will probably not impact more than a handful of people in the world, but that's fine.
Modified the static BIOS in -M to now show UEFI for actually UEFI booted systems, and, ideally,
UEFI [Legacy] for UEFI booting in bios legacy mode, and BIOS for all others. Hopefully this will
work ok, we'll see.
-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
A sloppy unescaped / triggered a failure I didn't notice in partition info.
Please update your inxi packages immediately if your version is 2016-03-21 or newer.
on /etc/issue step to first test for os release and not mint, then lsb verison and
not mint, then /etc/issue. This should keep the mint detection working well, as long
as they keep mint string in the /etc/issue file, that is, but that's out of our control.
test for the non deprecated battery test, /sys/class/power_supply/BAT0 existence.
This resulted in failure to indicate 'portable' where applicable.
I may also now add battery information where applicable since that's easy to get from
/sys
1. Add amdgpu to possible xorg drivers list (and gpu sensors data)
2. switch to default dig command to get WAN ip. This is usually but not always faster than
the http method. Because the IP source is not truly trustworthy (run by cisco), I'm keeping a
fallback mode on 1 second time out failure of the previous http based methods. Added dig
to recommended tools list.
NOTE: missing product name/serial info, because it's not being treated by linux kernel
as a standard disk. Could not find that data anywhere in the system debugger dump.
If you know how to find the model name/number and or serial, let me know.
Also small fix, as noted: ip: should be ip-v4 to match with ip-v6, thanks mikaela.
Also some debugger fixes and updates.
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.
showing Frameworks version, which is apparently NOT the same as the plasma version.
Also added debugger kde versioning to make this stuff less of an ordeal for data collection.
#kde-devel, now using kf5-config --version which gives similar output to kded4 --version
I use this for both 4 and 5, but since 4 has worked fine for years, I'll just use this for 5
and later.
normal, in this case, sddm decided that using a .pid or .lock file in /run was too easy
so they changed to some session id type string in the /run/sddm/ directory.
Speaking for myself, I find such pointless changes from anything resembling normal behaviors
to the reason that gnu freedesktop systems will never achieve significant desktop use globally.
Also, in the same vein, added debuggers to try to figure out what plasma5/kde 5 is using
internally to give command line version information. Again, something pointless internally
was changed, thus breaking something that had faintly resembled an api, which is of course
why desktop gnu linux will never actually take off, developers in the real world have no
interest in chasing after such pointless and never ending churn in even the most trivial
areas of the OS, let alone the core.
inxi remains however as a log of this ongoing churn and lack of discipline, and so remains
an interesting process of observation, and a way for users to try to avoid the constant
changes in simple system queries that should really never change, so I can see a reason
to keep it going since it's obvious that the actual foss ecosystem itself will not and apparently
cannot grasp that it is the lack of stable apis, methods, etc, that has kept desktop gnu linux
from achieving any actual real world success or popularity, and that is the actual problem
that should be fixed, not some pointless internal change to something.
On the source repo front, maintainers, I still can't find an acceptable alternative to the
impending shutdown of googlecode. github is a for profit venture that people who seem totally
void of any sense of history believe is actually going to be around longer than say, sourceforge,
or googlecode, as a legitimate source hosting site.
I'd welcome any suggestions. So far all the options are bad that I can find.
Top preference is svn, but if git is the absolute only other choice for an otherwise good option,
I'd consider git, but it's a horrible option for inxi because of how inxi development and debugging
works, vs how git works. ie, svn branches are perfect, git branches are totally wrong.
I may end up just hosting the svn on my own servers to avoid having to move yet again when the next
for profit flakey site decides to close up or monetize the source hosting.
The original idea of googlecode was for google to 'pay its dues to the foss community', but apparently
they got bored with that idea, plus of course, the ongoing total failure of google to deal with
automated spam, which has always been a huge bug in the core google corporate culture. But googlecode
was by far the best option I've come across, it was done by a deep pocketed corporation not for profit
for pretty good reasons, and was never intended to be a profit center, which is the closest I could
see for a non free option.
Setting up svn gui stuff however is a royal pain and requires ongoing maintainance for the life of
the software, which is NOT fun, nor will I sign up for that obligation.
I may end up moving to github anyway, even though git truly sucks for inxi and myself, but it's an
idea I find fairly vile, apparently free software (sic) authors seem to have no grasp of the concept
of fredom when it comes to source code hosting, judging by the absurd popularity of github as the
default go to source repo. Their website is pathetic as well, which isn't very promising.
So we'll see where it goes, I think I have until august to decide what to do for source hosting.
Since I'm old enough to have seen sourceforge and now googlecode do the same thing, along with a lot
of other options, to say github won't do this too is delusional, what you can almost certainly say is it
will do it, the only question is when. But, just as Linus did with his non free linux kernel version
control, people will stick with the non free stuff until you realize you can't use it anymore, because
it is non free. Free software hosted on non free source repos is to me one of the most absurd and
stupid things I've ever heard of to be honest.
the switched file name. Kudos to anyone out there fighting to create a working alternative
to the unreliable and buggy and windows emulating systemd, I wish devuan luck. Maybe between
devuan and gentoo and slackware we can save the free software core systems before it's too late.
pet peeve of mine. Now, if -I, -b, -F, or anything that can trigger the memory: used/total
in Information line is not used, -tm will always show the system used/total ram data on the
first line of the Memory item of -t output.
Also, if -xtc (trigger ram data in cpu output) is used, and -I is not triggered, and -tm is
not triggered, will also show system used/total ram data on the cpu first line.
I'd found it odd that this data did not appear when -tcm or -tm or -xtc were used, so this is
now fixed. I used the -t option a fair amount to find memory/cpu use issues, and usually I
don't use the option with other options, so the lack of total system ram data was odd.
long term solution to identify itself, so the hack I had in place fails on new MATE.
We'll see if this does it for various glitches, now quassel and mate latest should
again be working.
fine for all derived distros like Sabayon as well. The test looks for:
/etc/portage/repos.conf/ and type -p emerge
if found will then grab the repos from the source files found.
Note that the logic for this was almost identical to that used for rpm so it was an
easy addon. Please let us know if you have an issue and provide data samples of relevant
files.
1. Tightened runit init detection to use proc, note that if runit works on BSDs inxi will
require more data to properly detect it on BSDs..
2. Use openrc runlevel tests natively if openrc detected.
3. Fixed subtle issue with alias to inxi file and paths.
4. Added rc-status data collection for debugger, improved debugger data collector handling
of bsd and other tests to note absent if not there in file names.
Fixed bugs in Epoch init system detection, caused false positives in systems booted on
SysVinit, but with Epoch installed. Epoch turns out to be in PID 1 == epoch (/proc/1/comm)
so that's easy to fix.
Also fixed spacing isxue with OpenRC output in -I line.
at least on the system I got data from, is not using .pid/.lock extensions, but other systems
are, I'm adding sddm AND sddm.pid detection. This required changing the id to use explicit -f
for test, not the previous -e, which will force only files, not directories, to trigger yes case.
No other changes, but it's worth updating to this because distros may start using sddm in the not so
distant future, it's beta currently though.
as of yet unknown reasons, so rather than wait to see the bug resolved, I'm just removing
uptime as a depenendency, though this is a short term hack only because we don't know
why it was removed from procps or if that was just a mistake, or if other things as well might
be vanishing from procps. Am leaving in however uname as dependency because inxi cannot
determine what platform it is when it starts without that.
output for apt repos. Also refactored duplicated code into a function, no other changes.
Note that this version features the repo debugger tool as well, which is very helpful in
particularly non apt systems to fix issues with its handling of repo formats etc.
