From 5a20092c0bfeba0fdbb4b7c6a11aed32432022a6 Mon Sep 17 00:00:00 2001 From: Unit 193 Date: Wed, 20 Aug 2014 14:22:07 -0400 Subject: Imported Upstream version 2.2.00 --- inxi.changelog | 359 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 359 insertions(+) (limited to 'inxi.changelog') diff --git a/inxi.changelog b/inxi.changelog index c55328c..522a713 100755 --- a/inxi.changelog +++ b/inxi.changelog @@ -1,3 +1,362 @@ +===================================================================================== +Version: 2.2.00 +Patch Version: 00 +Script Date: 2014-08-18 +----------------------------------- +Changes: +----------------------------------- +New version, tarball, man page. Maintainers, this is the official release of -m feature. + +I have collected enough datasamples to allow for reasonably fine grained corrections, estimates, +warnings about unreliable capacity now, and have fixed all major failures. + +Also, because this stuff is filled out by people somewhere, or not, some fields often are just +empty, or contain the default values, ie, they are worthless. inxi shows N/A for those situations, +it means there is really no actual data to show you. + +This feature, sadly, well never be totally reliable, because dmi data is frankly junk, especially +dmi type 5 and 16, which is what is supposed to tell you total capacity of memory array, and the +maximum module size (type 5). However, this data is totally random, often it is right, sometimes +it is wrong. Sometimes type 5 is right and type 16 is wrong, sometimes the other way. And since +type 5 is only present in some systems, it's not reliable anyway. + +What is reliable and always right is the actually installed memory per device, ie, sticks. I have +not seen any errors in that, so that seems to be actually coming from the system itself. type 5 / 16 +sadly are clearly entered in manually by some poorly paid engineers out there in the world, and are +often total fictions, either far too small, or far too big, or whatever. + +inxi will attempt to correct all clear logic errors, and whenever it changes the listed data from +type 5/16, it notes either (est) or (check). (est) means it is a good guess, one I am comfortable making, +(check) means it is either an unreliable guess, or that what the system is reporting is so unlikely that +even though inxi is showing it, it doubts it could actually be true, or at least, it thinks you +should check this yourself. + +-m has 3 extra data options, -x prints the part number, if found, and the max module size, if type 5 +is present. inxi does NOT attempt to guess at max module size based on what is installed, it only will +correct a listed max module size if installed modules are > than listed max size. Usually part numbers, +if present, are all you need to order a new stick. + +-xx shows serial number, manufacturer (often empty, or just random alphanumeric identifiers, but sometimes +they list the actual company name, which is helpful. It also shows, if type 5 data is present, single/double +bank. + +-xxx as usual shows largely useless data that may be of interest to soemone, like if ram type is synchronous, +memory bus width data, and module voltage (type 5 data). + +This feature will never be reliable I am sad to say because the source data itself is random and much +has been filled out, or not filled out, by engineering drones somewhere out there in the underpaid +world. The ranges of errors are so wide that inxi just has to check what is possible, reasonable, unlikely, +etc, to generate its numbers. In other words, this is NOT just parsing dmidecode output, that is the raw +material only, sad to say. + +So this is it, for better or worse. All bug / issue reports with this MUST come with a full: +inxi -xx@14 +hardware data upload, run as root. + +Also, much to my annoyance, this feature requires root, since /dev/mem needs root to be read, and I assume +the dmi table, so that is a departure from normal inxi standards, as is the low quality input, and thus, +output, data, though I can guarantee that what inxi tells you is in most cases on average more accurate than +what dmidecode tells you, since dmidecode simply prints out what it finds in the dmi table, and nothing else, +in whatever order it finds it, from what I can see, ie, you also cannot trust the order of dmidecode output. + +I had been hoping that /sys would start to contain memory data like it does mobo/system data, but it never +happened so I finally decided to just do the ram thing, require dmidecode, require root/sudo, and that's +that. + +There will be issue reports, you can help them by looking up the mobo stats/specs yourself and listing them +in the issue, so I don't have to do it. I use the tool at crucial.com which is very accurate and also very +complete in terms of all possible hardware out there. + +I would trust that tool before trusting the companies that have the least reliable data, like ASUS. + +Much thanks to everyone who is contributing datasets, and the distros, particularly siduction, that really +were very helpful in this process, by finding more and more failure cases that helped me start to tighten +the logic, and make it more and more robust. Special thanks to Mikaela, of #smxi irc.oftc.net, who came up +with two systems that both required a full redo of the logic, and thus who helped a lot in this process. + +----------------------------------- +-- Harald Hope - Mon, 18 Aug 2014 15:07:36 -0700 + +===================================================================================== +Version: 2.1.98 +Patch Version: 01 +Script Date: 2014-08-17 +----------------------------------- +Changes: +----------------------------------- +New patch version, new tarball. Another error case dataset, wrong cap, wrong max mod +size, derived mod size 2gb, listed cap 8, but 2 slots, ie, 2gb x 2 == 4. Made this +retain the listed size, but adds (check) to it because either max mod size is wrong +or cap is wrong. + +----------------------------------- +-- Harald Hope - Sun, 17 Aug 2014 19:40:46 -0700 + +===================================================================================== +Version: 2.1.98 +Patch Version: 00 +Script Date: 2014-08-17 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball. Fixed bad assumption, DMI type 0 is not always before other +types, in at least one case, it is last, so can't use that as trigger to start loop. + +Now using: Table at .. which is always at start of dmi output. + +Also, changed size output per module to be in MB GB TB instead of all mB, since modules +are sold by GB or MB, the data should show that as well. Also shortens output. + +----------------------------------- +-- Harald Hope - Sun, 17 Aug 2014 12:01:38 -0700 + +===================================================================================== +Version: 2.1.97 +Patch Version: 00 +Script Date: 2014-08-16 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball. Another logic redo to handle a fringe case (dmidecode places +type 17 in front of type 16), now each array is created as a multidimenstional, 2x array, +and each device is a 3 dimensional array. This seems to clean up the problems with bad +ordering of dmidecode data. + +----------------------------------- +-- Harald Hope - Sat, 16 Aug 2014 16:22:17 -0700 + +===================================================================================== +Version: 2.1.96 +Patch Version: 02 +Script Date: 2014-08-15 +----------------------------------- +Changes: +----------------------------------- +forgot to remove debugger on switch +----------------------------------- +-- Harald Hope - Fri, 15 Aug 2014 16:55:04 -0700 + +===================================================================================== +Version: 2.1.96 +Patch Version: 01 +Script Date: 2014-08-15 +----------------------------------- +Changes: +----------------------------------- +Small change, forgot to add -m to the debugger inxi output. + +----------------------------------- +-- Harald Hope - Fri, 15 Aug 2014 16:43:47 -0700 + +===================================================================================== +Version: 2.1.96 +Patch Version: 00 +Script Date: 2014-08-14 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball, new man page. This version hopefully brings inxi closer to +at least making good guesses when the data is bad for ram, and hopefully will not break +too many cases where it was actually right but seemed wrong. + +Unfortunately, dmidecode data simply cannot be relied on, and is FAR inferior to the type +of data inxi tries in general to present users, ie, taken directly from the system, and, +ideally, more accurate than most other tools. But in this case, there is just no way to get +the data truly accurate no matter how many hacks I add. + +But if you have bad data, then submit: inxi -xx@ 14 so I can take a look at the system, +and see if I can modify the hacks to improve that data. + +----------------------------------- +-- Harald Hope - Thu, 14 Aug 2014 17:41:42 -0700 + +===================================================================================== +Version: 2.1.95 +Patch Version: 04 +Script Date: 2014-08-14 +----------------------------------- +Changes: +----------------------------------- +New patch version, tarball. Fixed a few small oversights, more debugging added. + +Will next try to handle the remaining corner cases if possible. +----------------------------------- +-- Harald Hope - Thu, 14 Aug 2014 12:23:38 -0700 + +===================================================================================== +Version: 2.1.95 +Patch Version: 01 +Script Date: 2014-08-13 +----------------------------------- +Changes: +----------------------------------- +patch version, trying to fix a small glitch with gawk wanting to change integers to strings. + +forcing int() on relevant items. + +----------------------------------- +-- Harald Hope - Wed, 13 Aug 2014 21:28:46 -0700 + +===================================================================================== +Version: 2.1.95 +Patch Version: 00 +Script Date: 2014-08-13 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball. Attempting to handle bad extra data for max module size, sometimes +it is too big, and sometimes too small. Changed data gathering to use arrays, then print/process +the arrays once they are assembled. + +Now it will get rid of any max module size if it's greater than the calculated capacity, and it +will generate an estimated capacity/max module size if they are clearly wrong because actual +module sizes are greater than listed max size, or capacity is less than greatest module sizes times +number of devices. + +Not perfect, but it never is, this covers more cases now correctly than before. + +----------------------------------- +-- Harald Hope - Wed, 13 Aug 2014 20:42:00 -0700 + +===================================================================================== +Version: 2.1.94 +Patch Version: 00 +Script Date: 2014-08-13 +----------------------------------- +Changes: +----------------------------------- +New version, new man page, new tarball. Realized that I can on some systems also add +maximum supported module size, and module voltage. Most systems do not have this data, +but some do. It's Type 5 item in dmidecode. + +Getting the type 6 data however is too hard, and even using type 5 assumes that the +system only has one physical memory array, but that's fine given how few systems +probably will have this information in the first place. + +----------------------------------- +-- Harald Hope - Wed, 13 Aug 2014 14:03:03 -0700 + +===================================================================================== +Version: 2.1.93 +Patch Version: 00 +Script Date: 2014-08-13 +----------------------------------- +Changes: +----------------------------------- +New version, new man page. Fixed man page errors, improved man page explanations of -m +features. Changed output syntax to be more consistent, now each main array line starts with: + +Array-X capacity: (where X is an integer, counting from 1) + +and each device line starts with: +Device-X: (where X is an integer incremented by 1 for each device, and starting at 1 +for each array. I have no data sets that contain > 1 physical memory array, if one appears, +I may need to patch the output to link the array handles with the device handles explicitly. + +Made memory bus width output more clear, and added in a hack to correct dmidecode output errors, +sometimes total width > data width, and sometimes data width is > total width, so using always +greatest value for total if not equal to other width. + +I think this will be close to it barring any user feedback or bugs, if nothing comes to +mind within a few days, I'll move the number to the new major version, 2.2.0 + +----------------------------------- +-- Harald Hope - Wed, 13 Aug 2014 12:12:23 -0700 + +===================================================================================== +Version: 2.1.92 +Patch Version: 00 +Script Date: 2014-08-12 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball. This is closer to final release. Removed Bank/Slot separate +items and am now just generating one: Locator item, usually from Slot/DIMM locator info, +but sometimes from Bank Locator info when it is more reliable based on my data samples. + +Updated help menu, updated man page, now shows working -x -xx -xxx extra data. This may +change slightly over time. + +Also removed speed output when No Module Installed is returned for device size. This +also wills switch off width if both total/data are empty. + +This is much closer now to live 2.2.0, but I'll leave a few more tests before putting +it at 2.2.0. + +----------------------------------- +-- Harald Hope - Tue, 12 Aug 2014 20:16:04 -0700 + +===================================================================================== +Version: 2.1.91 +Patch Version: 00 +Script Date: 2014-08-12 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball. This is a transitional version, most -x/-xx/-xxx data is now +working, but help/man does not have that yet, until I finalize the order. + +Fixed dmidecode issues, showing extra data types for -m, added line length handling +so -m is properly integrated with rest of inxi re max line lengths. + +----------------------------------- +-- Harald Hope - Tue, 12 Aug 2014 18:11:29 -0700 + +===================================================================================== +Version: 2.1.90 +Patch Version: 00 +Script Date: 2014-08-11 +----------------------------------- +Changes: +----------------------------------- +New version, new tarball, new man page. Finally, after all these years, initial memory/ram +support. This feature requires dmidecode, and usually that needs to be run as root. + +Significantly improved dmidecode error handling and output, and have as 2.1.90 testing/initial +release basic ram data. + +In subsequent releases, extra info for -x and -xx and -xxx will be added as well to the output. + +For those who want to jump on board early for ram data, update your repos, for those who want to +wait for the full featured version, with -x type data, wait for 2.2.0 + +And that's that. + +----------------------------------- +-- Harald Hope - Mon, 11 Aug 2014 22:23:18 -0700 + +===================================================================================== +Version: 2.1.29 +Patch Version: 00 +Script Date: 2014-08-08 +----------------------------------- +Changes: +----------------------------------- +No version change, this only will impact ancient systems, cleans up a data error message +and restores N/A to IF id in networking. No functional change, and won't be seen on any +non ancient systems. + +----------------------------------- +-- Harald Hope - Mon, 11 Aug 2014 16:10:03 -0700 + +===================================================================================== +Version: 2.1.29 +Patch Version: 00 +Script Date: 2014-08-08 +----------------------------------- +Changes: +----------------------------------- +New version, tarball. Big update/fix to -n/-i/-N. Now supports infiniband devices, which +have the odd feature in our test data of having > 1 IF id, like ib0 ib1 per pcibusid. + +Added support for virtual nics as well. This required refactoring the networking functions +significantly, so hopefully nothing breaks for existing systems. It should in theory be more +robust now than it was before, with more accurate output, particularly with multiple port +devices, like two port nics etc. + +----------------------------------- +-- Harald Hope - Fri, 08 Aug 2014 10:17:52 -0700 + ===================================================================================== Version: 2.1.28 Patch Version: 00 -- cgit v1.2.3