diff options
| author | 2023-07-10 18:43:07 -0400 | |
|---|---|---|
| committer | 2023-07-10 18:43:07 -0400 | |
| commit | c50367b90ae671eca05bc2ba553c9b7552e54996 (patch) | |
| tree | 1e3d8b80b6ec12f51884964a3c39bf62f7683da3 /inxi.1 | |
| parent | 444a30921e4fc5555e4152b2020004056cb53ae7 (diff) | |
| parent | 6ac681a6f39f057f92f2b52e5b629b235e71ccb1 (diff) | |
Update upstream source from tag 'upstream/3.3.28-1'
Update to upstream version '3.3.28-1'
with Debian dir 53259a62d7bbb2fb2a42dc48ee773de89f9539e3
Diffstat (limited to 'inxi.1')
| -rw-r--r-- | inxi.1 | 62 |
1 files changed, 50 insertions, 12 deletions
@@ -15,7 +15,7 @@ .\" with this program; if not, write to the Free Software Foundation, Inc., .\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. .\" -.TH INXI 1 "2023\-05\-07" "inxi" "inxi manual" +.TH INXI 1 "2023\-07\-10" "inxi" "inxi manual" .SH NAME inxi \- Command line system information script for console and IRC @@ -390,11 +390,7 @@ for extra information (init type/version, runlevel/target, packages). Note: if \fB\-m\fR or \fB\-tm\fR are active, the memory item will show in the main Memory: report of \fB\-m\fR/\fB\-tm\fR/, not in \fB\Info:\fR. -See \fB\-m\fR for explanation of \fBMemory: available:\fR. - -Raspberry Pi only: uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount, if -user is in video group and \fBvcgencmd\fR is installed. Uses this result to -increase the \fBMemory:\fR amount and \fBused:\fR amounts. +See \fB\-m\fR for explanation of \fBMemory:\fR fields and values.. .TP .B \-j\fR, \fB\-\-swap\fR @@ -548,7 +544,8 @@ If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds: .nf \fBMemory: - System RAM: available: 31.38 GiB used: 20.65 GiB (65.8%) + System RAM: total: 32 GiB note: est. available: 31.38 GiB + used: 20.65 GiB (65.8%) Array\-1: capacity: N/A slots: 4 note: check EC: N/A Device\-1: DIMM_A1 type: DDR3 size: 8 GiB speed: 1600 MT/s (800 MHz) Device\-2: DIMM_A2 type: DDR3 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) @@ -561,10 +558,49 @@ If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds: See \fB\-\-memory\-modules\fR and \fB\-\-memory\-short\fR if you want a shorter report. -Note: the \fBSystem Ram: available:\fR is actually the total installed RAM minus -some reserved and kernel code RAM (and in some cases GPU assigned main system -RAM) that is allocated on system boot, and thus is generally less than the -actual physical RAM installed. +Notes on \fBSystem RAM:\fR / \fBMemory:\fR report item: + +* \fBtotal:\fR and \fBigpu:\fR do not show for short form. + +* The \fBtotal:\fR can come from several possible sources: + +\- If not superuser, and if \fI/sys/devices/system/memory\fR exists, it will +estimate the total RAM based on how many RAM blocks and their size. Sometimes +the block count is not an exact match to installed RAM, and inxi will attempt to +guess the actual RAM amount, except for virtual machines. When it synthesizes +the actual physical RAM total, it will show \fBnote: est.\fR. + +Note that not all kernels are compiled to support generating this /sys +directory (kernel needs to be compiled with \fBCONFIG_MEMORY_HOTPLUG\fR). + +\- For OpenBSD and not superuser, the total comes from the detected RAM in +dboot, if available. + +\- If superuser, and if \fB\-m\fR used, it comes from the dmidecode RAM totals +if available, and if not, it comes from counting up the System RAM ranges in +\fI/proc/iomem\fR (Linux only), then rounding up, since that total is usually +slightly under the actual physical RAM total. If inxi is unsure about the total, +it will show \fBnote: est.\fB. + +If no total data found, shows \fBtotal: N/A\fB. + +* The \fBavailable:\fR item is the total installed RAM minus some reserved and +kernel code RAM (and in some cases iGPU assigned main system RAM) that is +allocated on system boot, and thus is generally less than the actual physical +RAM installed. This is called MemTotal in free/meminfo even though it isn't, +though it is the total available the kernel has to work with. + +* The \fBused:\fR is the percent of the available RAM used, NOT of the total +physical RAM. + +* The \fBigpu:\fR item either comes from Raspberry Pi gpu RAM, or from +\fI/proc/iomem\fR. The latter source is Linux + superuser only, and is not +guaranteed to be accurate, but sometimes is. That is for iGPU system RAM used, +not for standalone GPUs with their own internal RAM. Not all types of internal +VRAM are detectable, it depends on how the hardware assigns RAM to iGPU. + +Raspberry Pi uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount, if +user is in video group and \fBvcgencmd\fR is installed. .TP .B \-\-memory\-modules\fR, \fB\-\-mm\fR @@ -784,7 +820,7 @@ Make sure that there is no space between letters and numbers (e.g. write as If the \fB\-I\fR or \fB\-m\fR lines are not triggered, will also show the system RAM used/total information. -See \fB\-m\fR for explanation of \fBRAM: total\-available:\fR. +See \fB\-m\fR for explanation of \fBSystem RAM:\fR fields and values. .TP .B \-t cm\fR @@ -1486,6 +1522,8 @@ the sound API/server. .TP .B \-xx \-B\fR +\- Adds current power use, in watts. + \- Adds serial number. .TP |
