diff options
Diffstat (limited to 'inxi.changelog')
| -rw-r--r-- | inxi.changelog | 123 |
1 files changed, 109 insertions, 14 deletions
diff --git a/inxi.changelog b/inxi.changelog index 306d9a2..fd0ff52 100644 --- a/inxi.changelog +++ b/inxi.changelog @@ -1,4 +1,93 @@ ================================================================================ +Version: 3.3.12 +Patch: 00 +Date: 2022-01-18 +-------------------------------------------------------------------------------- +RELEASE NOTES: +-------------------------------------------------------------------------------- + +Small point release with some useful fixes, some bugs corrected, small +enhancement. + +-------------------------------------------------------------------------------- +KNOWN ISSUES: + +1. Note on KNOWN ISSUES 2 from 3.3.10, I realized that the second level +indentation actually takes care of that hanging parent, since now it's quite +clear that its children are indented on the following line. So that issue took +care of itself. + +-------------------------------------------------------------------------------- +BUGS: + +1. In $bsd_type cases, specifically SunOS triggered this, where sysctl was not +present (which it always is in all other BSD types), it tripped an error due to +failure to update to revised $alerts{'sysctl'}->{'message'}, instead was using +the old method. Failed to update that in refactor of CheckTools logic. Would +impact no supported operating systems, but is a bug. + +2. Corner case, a combination I never used, inxi -a, triggers error in the RAID +logic because the mdadm test was not run, generating an undefined eq error. Only +happened when mdraid was present and used on system. + +3. Tiny bug, for st+mt cpus, like alder lake, was printing out second tpc by +accident which made it look like it said st: 4 tpc: 2. Just a small output +glitch. + +-------------------------------------------------------------------------------- +FIXES: + +1. Added some fallback 32 bit system tests, [2345]86, like i386, i686. + +2. Changed shell: Unknown Shell to shell: N/A, that was a legacy use, and was +obviously redundant. N/A is more consistent with rest of output no value found +handling. Due to requirement of doing empty tests, this is set in the data, not +output, generator component. + +3. Refactored partition data logic to get rid of bsd tests for df -kTP, -kT, -k. +Now tests only to see if returns data, cascades down until it gets something. +Now will attempt to reconnect hanging lines when no -P feature available prior +to main partition data processing. This makes it agnostic to os issues, and it +just pays attention to feature support. + +Also adds in dynamic column count instead of hard-coded, this avoids oddities +and future proofs to some degree. Now systems will adapt seamlessly if support +for -P appears, or -T, or whatever. + +4. Partitions corner case, where has zram, but has no partitions, failed to show +partitions no data found message since @partitions had data in it, but nothing +for partitions output to print. Seen in TinyCore for example, but might happen +in other ram based systems. + +-------------------------------------------------------------------------------- +ENHANCEMENTS: + +1. Added Slint to distro ID, and slint/slackware to system base. + +-------------------------------------------------------------------------------- +CHANGES: + +1. None + +-------------------------------------------------------------------------------- +DOCUMENTATION: + +1. Typo in man page fixed. + +2. A few more edits and corrections on 3.3.10 changelong. That thing was written +concurrently with the development, and thus had lingering errors when things +were changed in midstream. + +-------------------------------------------------------------------------------- +CODE: + +1. Added --cygwin and --android fake system type flag. Switches on $b_android/ +$b_cygwin flags. + +-------------------------------------------------------------------------------- +-- Harald Hope - Tue, 18 Jan 2022 14:02:54 -0800 + +================================================================================ Version: 3.3.11 Patch: 00 Date: 2021-12-16 @@ -29,7 +118,7 @@ an undefined test from previous tests, not the right test, that is. Tripped error on Elbrus for example. 2. Typo in battery secondary type status, created undefined value error. This -was I believe an older bug. +was a recently created bug. -------------------------------------------------------------------------------- FIXES: @@ -41,15 +130,15 @@ tests to show stepping for elbrus revision. so L1 cache failed. 3. In cpuinfo fallback mode, Elbrus E2C3 cache data failed to appear, that data -in not per block in cpuinfo, but is the last block, so those tests had to run +is not per block in cpuinfo, but is the last block, so those tests had to run on each block, not just the first one. -------------------------------------------------------------------------------- ENHANCEMENTS: -1. Show for -Ca scaling min/max speeds if different from CPU min/max speeds. +1a. Show for -Ca scaling min/max speeds if different from CPU min/max speeds. -2. If no cpuinfo_min/max_freq speeds found, and scaling_min/max_freq found, set +1b. If no cpuinfo_min/max_freq speeds found, and scaling_min/max_freq found, set overall min/max to use scaling min/max instead of cpuinfo min/max. -------------------------------------------------------------------------------- @@ -102,7 +191,7 @@ inxi has bad output. Sidescrolling code blocks in forums in particular are absurdly hard to read and scan rapidly for data. Going along with the width and indentation changes, for most main row types, if -they wrap to a second row, they are further indented 2 column2, to make it +they wrap to a second row, they are further indented 2 columns, to make it easier to see what they belong to. The two levels of indentation contain more useful visual cues as to what belongs to what. @@ -123,10 +212,11 @@ KNOWN ISSUES: 1. Android seems to have CPU cache data, but does not show any 'size' item. But it does have the other data for each cache type internally, which is odd. -2. In some instances, the parent key:value pairs with '' as value, those are -parents of children key:value pairs, are left hanging at end of line, with the -children on the following line. This can look awkward, but in other cases, -actually looks very good, it depends if it's at the start or end of the line. +2. [See KNOWN ISSUES 2 for 3.3.12 above] In some instances, the parent key:value +pairs with '' as value, those are parents of children key:value pairs, are left +hanging at end of line, with the children on the following line. This can look +awkward, but in other cases, actually looks very good, it depends if it's at the +start or end of the line. I won't say this is not correctable, but it would be very difficult, and outside the scope of this release, but that is something that I may look at for a future @@ -237,9 +327,8 @@ dmidecode type 4 found, and if physical cpu counts equal 1, then replace the found counts with the dmidecode physical cpu counts. 11. Corrected bad assumption that threads would always be 2 per core for MT -tests. Still no way to reliably determine threads per core for non x86 cpus like -powerpc however, but those are very fringe and should rarely be an issue since -that data is only missing on very old linux now I think. +tests. Revised logic should handle this case fine now, and show correct thread +count per core. 12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to. -S is two lines, the kernel / host stuff, and the desktop/console/distro stuff. @@ -247,7 +336,7 @@ that data is only missing on very old linux now I think. 13. Fixed case when key: value first word plus other parts of line longer than max width, failed to wrap as expected. -14. Added start/end ' and " start / end \s to main filters. +14. Added start/end ' and " to existing start / end \s trims to main filters. -------------------------------------------------------------------------------- ENHANCEMENTS: @@ -273,7 +362,13 @@ perforance cores. This should also in theory show different the different min/max speeds if they were detected. Those did not seem to be set correctly in Alder Lake sample data -I saw however, P and E cores were set to the same min/max speeds. +I saw however, P and E cores were set to the same min/max speeds. + +[Update 3.3.12: more research suggests that for now, 1 cpu physical body will +contain one clock generator, so that is not a mistake. Future CPUs may add a +second clock generator but that is probably very complicated to implement, which +is why ARM complex cpus simply use two cpus, with different clock rates when +they want to run different speeds for efficiency.] 5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing), and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU |