Why does the Chromebook see so little RAM?

Question

linux

Good afternoon.
I purchased a Toshiba Chromebook 2 (2014) "Swanky" Chromebook Model: CB35-B3340
The following characteristics are indicated on the manufacturer's website:

1. Processor: Intel Celeron N2840
   
2. Operating System: Chrome OS
   
3. Graphics engine: Intel HD Graphics
   
4. Memory: 4GB DDR3 1600MHz
   
5. Hard drive: 16GB solid state flash memory (eMMC)
   

Flashed the bios, reinstalled another operating system.
Now I'm using Elementary OS.
The internet is full of instructions.
Everything works, everything suits, everything is gorgeous.
The question is why the system sees only 2 gigs of RAM out of 4?
Where did the other 2 gigs go?

[email protected]:~$ cat /proc/meminfo
MemTotal:        1964540 kB
MemFree:          198020 kB
MemAvailable:     237668 kB
Buffers:            4888 kB
Cached:           544920 kB
SwapCached:        16416 kB
Active:          1171608 kB
Inactive:         442876 kB
Active(anon):    1081700 kB
Inactive(anon):   395880 kB
Active(file):      89908 kB
Inactive(file):    46996 kB
Unevictable:        1788 kB
Mlocked:            1788 kB
SwapTotal:       2010108 kB
SwapFree:        1540484 kB
Dirty:               332 kB
Writeback:             0 kB
AnonPages:       1064884 kB
Mapped:           293236 kB
Shmem:            412912 kB
Slab:              59232 kB
SReclaimable:      30736 kB
SUnreclaim:        28496 kB
KernelStack:        7952 kB
PageTables:        40308 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     2992376 kB
Committed_AS:    6210144 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      548864 kB
VmallocChunk:   34359123872 kB
HardwareCorrupted:     0 kB
AnonHugePages:    120832 kB
CmaTotal:              0 kB
CmaFree:               0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      152944 kB
DirectMap2M:     1859584 kB

[email protected]:~$ cat /var/log/Xorg.0.log | grep -i driver
[    10.458] 	X.Org Video Driver: 19.0
[    10.458] 	X.Org XInput driver : 21.0
[    10.480] (==) Matched intel as autoconfigured driver 0
[    10.480] (==) Matched intel as autoconfigured driver 1
[    10.480] (==) Matched modesetting as autoconfigured driver 2
[    10.480] (==) Matched fbdev as autoconfigured driver 3
[    10.480] (==) Matched vesa as autoconfigured driver 4
[    10.480] (==) Assigned the driver to the xf86ConfigLayout
[    10.481] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[    10.487] 	Module class: X.Org Video Driver
[    10.487] 	ABI class: X.Org Video Driver, version 19.0
[    10.487] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    10.488] 	Module class: X.Org Video Driver
[    10.488] 	ABI class: X.Org Video Driver, version 19.0
[    10.488] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    10.489] 	Module class: X.Org Video Driver
[    10.489] 	ABI class: X.Org Video Driver, version 19.0
[    10.489] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    10.490] 	Module class: X.Org Video Driver
[    10.490] 	ABI class: X.Org Video Driver, version 19.0
[    10.490] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
[    10.491] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[    10.491] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[    10.491] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[    10.491] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    10.491] (II) FBDEV: driver for framebuffer: fbdev
[    10.491] (II) VESA: driver for VESA chipsets: vesa
[    10.493] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20141121
[    10.497] 	ABI class: X.Org Video Driver, version 19.0
[    10.552] (II) intel(0): [DRI2]   DRI driver: i965
[    10.552] (II) intel(0): [DRI2]   VDPAU driver: i965
[    10.877] 	Module class: X.Org XInput Driver
[    10.877] 	ABI class: X.Org XInput driver, version 21.0
[    10.877] (II) Using input driver 'evdev' for 'Power Button'
[    10.879] (II) Using input driver 'evdev' for 'Power Button'
[    10.881] (II) No input driver specified, ignoring this device.
[    10.882] (II) Using input driver 'evdev' for 'Sleep Button'
[    10.883] (II) Using input driver 'evdev' for 'Sleep Button'
[    10.885] (II) Using input driver 'evdev' for 'Telink Wireless Receiver'
[    10.887] (II) No input driver specified, ignoring this device.
[    10.888] (II) Using input driver 'evdev' for 'Telink Wireless Receiver'
[    10.889] (II) Using input driver 'evdev' for 'TOSHIBA Web Camera - HD'
[    10.893] (II) No input driver specified, ignoring this device.
[    10.893] (II) No input driver specified, ignoring this device.
[    10.894] (II) No input driver specified, ignoring this device.
[    10.897] 	Module class: X.Org XInput Driver
[    10.897] 	ABI class: X.Org XInput driver, version 21.0
[    10.897] (II) Using input driver 'synaptics' for 'Elan Touchpad'
[    11.002] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'

[email protected]:~$ free
             total       used       free     shared    buffers     cached
Mem:       1964540    1609940     354600     374744      14660     567552
-/+ buffers/cache:    1027728     936812
Swap:      2010108     465708    1544400
[email protected]:~$

Answer 1

I know from experience that this occurs when installing ubuntu-based distributions on chromebok. At the same time, Arch and Manjaro see the full 4 gigabytes. However, with what it is connected and how to solve this problem, unfortunately, I will not tell you.

Answer 2

Show sudo dmidecode. I suspect that you still have 2 gigs, not 4. They could change it during resale.