new inxi feature: -m for ram/memory - request for comment/data
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Latest svn inxi: 2.1.94

This is close to what will be released as 2.2.0, unless someone can show bugs or failures etc.

The output has been tested on a wide range of user datasets (thanks to all the people who keep supplying inxi with new data sets via inxi -xx@ 14 I couldn't do this type of feature without them.

I was actually surprised how many people had run inxi -xx@ 14 as root, which gave me the required dmidecode output, more than I thought I would have gotten.

:: Code ::
sudo inxi -mxxx
Memory:    Array-1 capacity: 8 GB devices: 4 EC: No
           Device-1: DIMM0 size: 2048 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-2: DIMM1 size: 2048 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-3: DIMM2 size: 1024 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-4: DIMM3 size: 1024 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A


this is a good use of sudo too by the way, usually I just go to root, but in this case, sudo is just right.

This is my dataset, others look more complete:
:: Code ::
Memory:   Array-19 capacity: 16 GB devices: 2 EC: No
           Device-1: ChannelA-DIMM0 size: 4096 MB speed: 1067 MHz type: DDR3 (Synchronous)
           bus width: 64 bits manufacturer: ELPIDA part: EBJ41UF8BCS0-DJ-F serial: 522C70BA
           Device-2: ChannelA-DIMM1 size: No Module Installed type: N/A
           Device-3: ChannelB-DIMM0 size: 2048 MB speed: 1067 MHz type: DDR3 (Synchronous)
           bus width: 64 bits manufacturer: ELPIDA part: EBJ20UF8BCS0-DJ-F serial: 55922ADE
           Device-4: ChannelB-DIMM1 size: No Module Installed type: N/A


Any comments or bugs or failures etc, this is the time to report them.

Note, if you use a distro packaged inxi and your inxi -U is blocked, just edit your /etc/inxi.conf file, and change:
:: Code ::
B_ALLOW_UPDATE=false

to
:: Code ::
B_ALLOW_UPDATE=true

then save that file, and run: inxi -U to get latest version.

ADDED: 2.1.94
:: Code ::
Memory:    Array-1 capacity: 8 GB devices: 4 EC: None max module size: 2048 MB module voltage: 3.3 V
           Device-1: DIMM0 size: 2048 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-2: DIMM1 size: 2048 MB speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A

Back to top
GoinEasy9
Status: Contributor
Joined: 28 Jun 2008
Posts: 84
Location: Manorville, New York
Reply Quote
I still have an aversion to using sudo, but, using root works just fine.

:: Code ::
# inxi -S -I -mxxxx
System:    Host: siduction64kdefx Kernel: 3.16-1.towo-siduction-amd64 x86_64 (64 bit gcc: 4.9.1)     
           Desktop: KDE 4.13.3 (Qt 4.8.6) info: plasma-desktop dm: lightdm     
           Distro: siduction 13.2.0 December - kde - (201312310241)     
Memory:    Array-1 capacity: 32 GB devices: 4 EC: Multi-bit ECC
           Device-1: DIMM0 size: 4096 MB speed: 533 MHz type: DDR3     (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A     
           Device-2: DIMM1 size: 4096 MB speed: 533 MHz type: DDR3     (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A     
           Device-3: DIMM2 size: 4096 MB speed: 533 MHz type: DDR3     (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A     
           Device-4: DIMM3 size: 4096 MB speed: 533 MHz type: DDR3      (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A     
Info:      Processes: 260 Uptime: 1:09 Memory: 1257.1/16001.0MB
           Init: systemd v: 208 runlevel: 5 default: 5 Gcc sys: 4.9.1 alt: 4.8
           Client: Shell (bash 4.3.221 running in konsole) inxi: 2.1.94

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
2.1.98 brings inxi very close to final release of 2.2.0, every day I'm getting new datasets for systems that did not work as expected, sometimes the glitches are caused by the things done the day before, so that's good to get them.

:: Code ::
Memory:    Array-1 capacity: 8 GB devices: 4 EC: None max module size: 2 GB
           Device-1: DIMM0 size: 2 GB (Double-bank) speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-2: DIMM1 size: 2 GB (Double-bank) speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-3: DIMM2 size: 1 GB (Single-bank) speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
           Device-4: DIMM3 size: 1 GB (Single-bank) speed: 400 MHz type: DDR2 (Synchronous)
           bus width: 64 bits (total: 72 bits) manufacturer: N/A part: N/A serial: N/A
Info:      Processes: 267 Uptime: 13 days Memory: 4266.5/6078.7MB
           Init: SysVinit v: 2.88 runlevel: 3 default: 3 Gcc sys: 4.8.2 alt: 4.0/4.2/4.4/4.5/4.6/4.7
           Client: Shell (sudo running in bash) inxi: 2.1.98


Note some of the data is not always there, as you can see, in my dev system, there's no manu/serial data, or part nu. Others will have no max module size, or no (singl/double bank) type extra data. Still others have no type data, a few have corrupted location data so they show N/A there. Basically the dmi table data is junk, and does not have any necessary relationship to what is actually in the system, particularly when it comes to the physical memory array line, with capacity/max capacity, those can be and often are pure fictions, that inxi will try to correct, and when it does, you will see either (est) or (check) after it. check means it's a guess highly unreliable so you should check the system spscs. est will be usually close, though it can be too low depending on your max actually installed ram size.
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 95
Reply Quote
:: Code ::
# inxi -mxxx
Memory:    Array-1 capacity: 32 GB devices: 4 EC: None
           Device-1: DIMM0 size: No Module Installed type: N/A
           bus width: 64 bits
           Device-2: DIMM1 size: 4 GB speed: 933 MHz
           type: DDR3 (Synchronous Unbuffered (Unregistered)) bus width: 64 bits
           manufacturer: N/A part: F3-1866C9-4GAB serial: N/A
           Device-3: DIMM2 size: No Module Installed type: N/A
           bus width: 64 bits
           Device-4: DIMM3 size: 4 GB speed: 933 MHz
           type: DDR3 (Synchronous Unbuffered (Unregistered)) bus width: 64 bits
           manufacturer: N/A part: F3-1866C9-4GAB serial: N/A


This is from the G.skill Ares F3-1866C9D-8GAB DDR3-1866 PC3-14900 4096MBx2 CL9-10-9-28 1.5V[/code]
Back to top
Display posts from previous:   

All times are GMT - 8 Hours