inxi 2.1.96 now released, this has modified many hacks to get right max capacity.
If your system shows wrong wrap data, then please run: inxi -xx@14
so I can get the debugger data, run as root.
Or, show output of: inxi -bmxxx
so I can check the system board specs myself, or post the specs, but I can't debug the system ram without the full debugger data set, run as root.
What I'm doing is taking the datasets that I have and running them as huge memory sets of data and then debugging them one by one until the stuff I have works as expected, but it's purely emprical, ie, Iam making specific systems work, which can break other systems that were working.
My conclusion is that it is impossible to get this data right untili the actual linux kernel can give the true ram data via /sys, otherwise it's subject to the same failures all data of this type is, totally random entries into various fields, mostly in the capacity/max module size, the other stuff seems to be mostly right as far as I can tell.
I'll do a few more patches on 2.1.96 but then I think I will call it good enough, otherwise this can take forever.
The more data sets I get, the better, however.
If the system has a wrong max capacity, without (est) or (check), then that's coming from the system itself not inxi, so make sure to give me the: inxi -xx@ 14 for that system, as root. In most cases this will be a capacity that is too high, not too low, the too low is easier to handle by tests, but too high is basically impossible to handle in most cases. Items that are like this: 32 gB (est OR check) however that are wrong can probably be fixed, or at least improved once I have the data.
I thought about 20 data sets would be enough, but it looks like about 50 may be needed to really get the stuff consistent, though with each release I believe a higher percentage of systems will be right, and those that are wrong, will be less wrong, though some will be way off.