diff options
Diffstat (limited to 'inxi.changelog')
| -rw-r--r-- | inxi.changelog | 174 |
1 files changed, 167 insertions, 7 deletions
diff --git a/inxi.changelog b/inxi.changelog index a16d6c8..0832fad 100644 --- a/inxi.changelog +++ b/inxi.changelog @@ -1,4 +1,152 @@ ================================================================================ +Version: 3.3.24 +Patch: 00 +Date: 2022-12-10 +-------------------------------------------------------------------------------- +RELEASE NOTES: +-------------------------------------------------------------------------------- + +A small point release, mainly to get some bug fixes, and a few minor issues, and +some ongoing updates to various matching rule features like CPU, Disk Vendors, +etc. + +-------------------------------------------------------------------------------- +SPECIAL THANKS: + +1. mrmazda, for continuing to poke around and finding oddities on occasion. + +2. The various packagers, for continuing to package inxi. + +3. Nothing else really comes to mind, so I'm thankful that no real issues popped +up, and the ongoing attempt to stabilize and clean up the several year +aggressive development cycle of code is proceeding quite well. + +-------------------------------------------------------------------------------- +KNOWN ISSUES: + +1. I'm currently getting no data samples from new server type CPU systems, +Nvidia Grace, Ampere, both ARM V2 based. The ARM cpu arch logic hasn't been +updated in many years since I have gotten no meaningful data, currently +Raspberry Pi 4 is the latest ARM generation I've seen data for, and no ARM +server type for many years. So support there is really not happening, and won't +be until I start getting real datasets on those server systems. + +Nvidia uses Neoverse V2 ARM core, but I have no information on that yet. Also +nothing from the Amazon CPU, new Marvell datacenter type CPUs. But that's not +surprising.Also, nothing from the N1 (2019) or V1 Neoverse (2021) ARM CPU family +even though those have now been out a while. + +A lot of the advanced CPU data should 'just work' because of the huge CPU +refactor done recently, but some of the more advanced data, particularly +cpu_arch type data, isn't going to be available until I get real data sets so I +can see what's going on. No idea how CPUID might work for ARM cpus, for example. + +Objectively many of these datacenter/machine learning focused CPUs will never +see a system inxi will run on, though most I suspect will be running GNU/Linux +in some form, so inxi can in theory run on them, but those people all know what +their systems are doing, so the need isn't particularly pressing of course. + +With this said, I did used to have more access to cutting edge server stuff, but +that has largely dried up, particularly ARM based chips. + +-------------------------------------------------------------------------------- +BUGS: + +1. Found while resolving Fix 2, it turns out > 1 X Screens would not have shown +correctly due to failing to pass $j row counter by reference. This bug was +introduced when the big Monitor updates were done, since you almost never see +> 1 X Screens now, I never saw it until testing something for another reason. + +This led to > 1 Screen showing on the same line as the last monitor of the +previous Screen. + +See also Fixes 2, 3, 4, and Code 1, 2, 3. + +-------------------------------------------------------------------------------- +FIXES: + +1. Changed Intel Saphire Rapids release data from 2021+ (what Intel had +initially announced) to 2023+ (the actual release date). Not my fault!! They +were too optimistic, inxi merely repeated their claims. + +2. While trying to figure out extra Screen showing up, found a series of subtle +issues with how X Screens are handled. Added in more robust test for if Screen +ID has been added by xdpyinfo_data, and other weird corner cases that might +cause strange results in Display Screen-x. + +Created check_screen() to allow for more granular and debugable testing. + +This forum post helped focus attention on this issue: + +https://forum.endeavouros.com/t/\ +my-second-screen-is-not-working-after-installing-nvidia/33388 + +3. %monitors was not correctly assigned in xrandr screen fallback. + +4. Set number of Screens found if no xdpyinfo or if xrandr found > xdpyinfo +number of screens. + +5. Added Zhaoxin match to Centaur match, might show up on cpu string. + +6. OpenBSD's package manager was listed as pkg_info, but it's slightly more +accurate to call it pkg_add. As far as I understand it, OpenBSD doesn't really +have a 'package manager' per se, it has a suite of tools to manage packages. + +-------------------------------------------------------------------------------- +ENHANCEMENTS: + +1. Added some Zhaoxin/Centaur IDs, unlikely to show up, but you never know. + +2. Added m68k to X display driver list. This was just added to kernel as a full +drm driver! Very legacy, but has users in vm, qemu, etc. + +3. More disk vendors! I skipped updating this last time because, well, +collecting the data is really boring, and slightly tedious, and really serves to +simply remind that this is not the way towards a better world. Or are cheap SSDs +the true path after all? I doubt it, but you never know. + +4. New AMD, Nvidia gpu ids. + +5. New Intel Cpu Microarch IDs. + +-------------------------------------------------------------------------------- +CHANGES: + +1. No changes to speak of, so I won't. + +-------------------------------------------------------------------------------- +DOCUMENTATION: + +1. Various ongoing updates to inxi-perl/docs. These are very slowly being pulled +into a more useful form. Emphasis on slowly. + +-------------------------------------------------------------------------------- +CODE: + +1. In Graphics::xdpyinfo_data() and Graphics::xrandr_data() got rid of extra +step, now just assign hash reference directly to push anonymous hash reference +into array. Had used intermidiate variable assignement of hash ref, but that is +pointless. + +2. Added $fake{'xdpyinfo'}, hoping to get some debugger data to test weird +extra 'Screen' seen with Endeavor user (see Fix 2, 3, Bug 1). + +3. Also, instead of using \%monitors, which creates a reference to the last +value of %monitors, used the correct and safer {%monitors}, which creates an +anonymous reference of the value %monitors had at that moment. This is a subtle +Perl error which is easy to make in cases where the hash or array reference is +almsot never > 1 instance, such as > 1 X Screens. + +This should at least help resolve the repeated 'monitors' rows in the output +in Fixes 2, 3, 4. + +4. Added 'source' to $graphics{'screens'} to log where each detected screen came +from, xdpyinfo or xrandr. + +-------------------------------------------------------------------------------- +-- Harald Hope - Sat, 12 Dec 2022 13:28:23 -0700 + +================================================================================ Version: 3.3.23 Patch: 00 Date: 2022-10-31 @@ -7,11 +155,9 @@ RELEASE NOTES: -------------------------------------------------------------------------------- This release fixes another very long standing bug, which I was not sure was an -inxi or a Konversation bug, which made tracking it down very difficult. Special -thanks to argonel of Konversation for helping solve this problem, or at least, -for directing my attention towards the likely cause area, and away from wrong -ideas. The bug was that inxi simply did not run in Konversation, it would exit -with error when run with /cmd or /inxi via symbolic links. +inxi or a Konversation bug, which made tracking it down very difficult. The bug +was that inxi simply did not run in Konversation, it would exit with error when +run with /cmd or /inxi via symbolic links. This may not seem like a huge deal to many of you, but the actual history of inxi was directly linked to user support in mainly Konversation, so this feature @@ -41,6 +187,21 @@ deserved, breather, to recover after huge increases in the overall LOC and feature sets. -------------------------------------------------------------------------------- +SPECIAL THANKS: + +1. MrMazda, for finding even more failure and corner case issues. See Bug 1. + +2. Github Issue #275, for finding and reporting and testing some WSL failures. + +3. argonel of Konversation, for helping me finally track down the inxi / pinxi +failing to run in Konversation issue. Done, appropriately, on IRC channel +#Konversation. And in particular, for directing my attention towards the likely +cause area, and away from wrong ideas. + +4. Thanks delanym, who filed Gitbub issue #276 for reporting a ZFS problem, +which also exposed some harder to trigger bugs in ZFS (Bug 3). + +-------------------------------------------------------------------------------- KNOWN ISSUES: 1. No known way to detect that the system might be Wayland for the Graphics:.. @@ -123,8 +284,7 @@ PYTHONPATH is not present with konversation string present as well. 5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs, which can lead to wrong usable disk total size report, along with failure -to show components. Thanks delanym, issue #276 for reporting this problem, which -also exposed some harder to trigger bugs in ZFS (Bug 3). +to show components. 6. Exposed by issue #276, case where line was wrapping value when value was too short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words |