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.
Bugs:
1. See fix 4, incorrect positioning of Trinity desktop detection logic.
Fixes:
1. Vascom reports in issue #169 that some systems are making the /sys cpu
vulnerability data root read only. Added <root required> test and output.
2. A while back, they added several chassis types in the smbios
specifications. I used an older specification pdf file, this is now corrected.
Note that realworld use of the new types exists, like tablet, mini pc, and so
on. This missing data caused Machine report to list N/A as machine type when
it was actually known. I'd been using an older specification PDF, and had
failed to look at the actual spec download page, where you could clearly see
the newer spec file. Corrected this in the inxi docs as well.
3. Made gentoo repo reader check for case insensitive values for enabled.
Also extended that to other repo readers that use similar syntax, they are
all now case insensitive (Yes/yes/YES, that is)
4. Fixed incorrect handling of Trinity desktop ID, that needed to happen in
the kde ID block, as first test, not after it. Caused failure in Q4OS trinity,
and maybe others. I'm not sure why inxi had the detection where it was, it
made no real sense, so that's now nicely integrated, so these types of
failures should not happen again. Thanks Q4OS for exposing that issue.
Enhancements:
1. Added TDM and CDM display managers. Never seen either (Q4OS uses TDM), TDM
corrected. CDM not confirmed, don't know if it's still around, but if it is
similar to TDM re cdm.pid in /run, it should be detected fine.
2. Added more disk vendors/ids, the list never stops!! Thanks LinuxLite
Hardware database, your users seem to use every disk known to humanity.
3. Added Debian derived Q4OS distro ID and system base handler.
Bugs:
1. ARM fix, odroid > 1 cpu speeds not showing correctly.
2. Ansible start fixes.
3. Fringe Battery failures, see Pinebook.
Fixes:
1. Removed null data message 'old system' since that's not always the case.
2. Added support for > 1 CPU speeds in systems with > 1 CPU.
3. Added is_numeric test for sudo version tests, that was tripping errors in
rare cases.
4. Fine tuned terminal size setting to check that is int to correct the
Ansible problem.
5. ARM Pinebook fixes, battery, cpu. This also fixes corner cases where
the battery charge state is missing but it is a systme battery.
Enhancments:
1. Added more disk ID matches/vendors. Thanks LinuxLite Hardware database!!
2. UKUI, ukwm, ukui-panel added to desktop data.
3. Added PopOS to system base.
4. Ansible/Chef user noted that inxi believes that it is running in IRC when
started by Ansible / Chef (not sure about Chef but assuming it's the same).
Added flag --tty flag to force inxi to believe it's running in shell no matter
what starts it. Note that this fix is not confirmed because the person didn't
confirm the fix. Annoying.
5. Added Ubuntu disco to ubuntu_id.
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.
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!
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.
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.
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
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.
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
