RAM not correctly detected after install

Hi!

I’ve reinstalled EndeavourOS (along with Windows 10) and at first startup RAM is not detected correctly. Instead of 16GB only 1.59GB is detected and used (My laptop is laggy and a few browser tabs freeze it).

$ inxi -Fxxxz

System:    Kernel: 5.8.10-arch1-1 x86_64 bits: 64 compiler: N/A Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm 
           dm: LightDM 1.30.0 Distro: EndeavourOS 
Machine:   Type: Laptop System: Acer product: Swift SF514-54T v: V1.14 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: IL model: Yebisu_IL v: V1.14 serial: <filter> UEFI: Insyde v: 1.14 date: 05/06/2020 
Battery:   ID-1: BAT0 charge: 37.3 Wh condition: 55.3/56.0 Wh (99%) volts: 15.2/15.4 model: SMP KT00407008 AP18C7M 
           type: Li-ion serial: <filter> status: Discharging cycles: 144 
CPU:       Info: Quad Core model: Intel Core i7-1065G7 bits: 64 type: MT MCP arch: Ice Lake rev: 5 L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23968 
           Speed: 863 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 862 2: 964 3: 1037 4: 757 5: 755 6: 729 7: 1068 8: 780 
Graphics:  Device-1: Intel Iris Plus Graphics G7 vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:8a52 
           Device-2: Chicony HD WebCam type: USB driver: uvcvideo bus ID: 3-6:3 chip ID: 04f2:b5c5 serial: <filter> 
           Display: x11 server: X.Org 1.20.9 compositor: budgie-wm driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz s-dpi: 96 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: Intel Smart Sound Audio vendor: Acer Incorporated ALI driver: sof-audio-pci bus ID: 00:1f.3 
           chip ID: 8086:34c8 
           Sound Server: ALSA v: k5.8.10-arch1-1 
Network:   Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel port: 3000 
           bus ID: 00:14.3 chip ID: 8086:34f0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 476.94 GiB used: 120.46 GiB (25.3%) 
           ID-1: /dev/nvme0n1 vendor: Kingston model: RBUSNS8154P3512GJ1 size: 476.94 GiB speed: 15.8 Gb/s lanes: 2 
           serial: <filter> rev: E8FK12.3 scheme: GPT 
Partition: ID-1: / size: 77.84 GiB used: 7.33 GiB (9.4%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-2: /home size: 154.84 GiB used: 113.07 GiB (73.0%) fs: ext4 dev: /dev/nvme0n1p7 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 265 Uptime: 10m Memory: 1.59 GiB used: 828.8 MiB (51.0%) Init: systemd v: 246 Compilers: gcc: 10.2.0 
           Packages: pacman: 915 Shell: Bash v: 5.0.18 running in: gnome-terminal inxi: 3.1.06 

I’ve restarted the system and booted with fallback initramfs. RAM is detected correctly.

$ inxi -Fxxxz

System:
  Kernel: 5.8.10-arch1-1 x86_64 bits: 64 compiler: N/A 
  Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm dm: LightDM 1.30.0 
  Distro: EndeavourOS 
Machine:
  Type: Laptop System: Acer product: Swift SF514-54T v: V1.14 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: IL model: Yebisu_IL v: V1.14 serial: <filter> UEFI: Insyde v: 1.14 
  date: 05/06/2020 
Battery:
  ID-1: BAT0 charge: 35.3 Wh condition: 55.3/56.0 Wh (99%) volts: 15.4/15.4 
  model: SMP KT00407008 AP18C7M type: Li-ion serial: <filter> 
  status: Discharging cycles: 144 
CPU:
  Info: Quad Core model: Intel Core i7-1065G7 bits: 64 type: MT MCP 
  arch: Ice Lake rev: 5 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 23968 
  Speed: 1043 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 1075 2: 995 
  3: 1051 4: 701 5: 992 6: 838 7: 709 8: 748 
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Acer Incorporated ALI 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:8a52 
  Device-2: Chicony HD WebCam type: USB driver: uvcvideo bus ID: 3-6:3 
  chip ID: 04f2:b5c5 serial: <filter> 
  Display: x11 server: X.Org 1.20.9 compositor: budgie-wm driver: intel 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 
  Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:
  Device-1: Intel Smart Sound Audio vendor: Acer Incorporated ALI 
  driver: sof-audio-pci bus ID: 00:1f.3 chip ID: 8086:34c8 
  Sound Server: ALSA v: k5.8.10-arch1-1 
Network:
  Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter 
  driver: iwlwifi v: kernel port: 3000 bus ID: 00:14.3 chip ID: 8086:34f0 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 120.46 GiB (25.3%) 
  ID-1: /dev/nvme0n1 vendor: Kingston model: RBUSNS8154P3512GJ1 
  size: 476.94 GiB speed: 15.8 Gb/s lanes: 2 serial: <filter> rev: E8FK12.3 
  scheme: GPT 
Partition:
  ID-1: / size: 77.84 GiB used: 7.34 GiB (9.4%) fs: ext4 dev: /dev/nvme0n1p6 
  ID-2: /home size: 154.84 GiB used: 113.07 GiB (73.0%) fs: ext4 
  dev: /dev/nvme0n1p7 
Swap:
  Alert: No Swap data was found. 
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 247 Uptime: 2m Memory: 15.32 GiB used: 904.8 MiB (5.8%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 915 
  Shell: Bash v: 5.0.18 running in: gnome-terminal inxi: 3.1.06 

This situation is also accompanied by inability to access BIOS menu. It hangs when I want to boot into BIOS menu.

In the end I learned how to fix it. I use efibootmgr to delete some junk boot entries which are always there (that means that they reappear after reboot). After deleting them I can access BIOS menu and RAM is correctly detected.

I know I created those boot entries manually in the past trying to solve some boot issue with another system (I don’t remember well). Anyway, I don’t have enough knowledge to understand what’s happening. I just discovered an “algorithm” to fix this issue that appears (almost or not) any time i install a fresh system. Maybe it’s a very specific problem caused by those boot entries which happens only on my laptop. However, I thought it’s worth posting it, maybe somebody more experienced sees something I can’t see.

  1. Does UEFI (BIOS) see full RAM?
  2. Does Windows 10 see full RAM?
  3. Check it with memtest from EndeabourOS live-USB (if it will give errors or dead - sadly you’ll have to change whole laptop / motherboard, since it’s soldered RAM)

btw it’s not advisable to dual-boot with Windows 10, it’s not safe anymore:

So at least know your risks :slight_smile:

P.S. @ricklinux yep and installed as UEFI, he already said in other thread :wink:

Is your system UEFI?

Other thread? Just wondered because people call it Bios which is not correct if it’s UEFI. Bios is legacy and UEFI is a firmware not a BIOS. It confuses the issue.

1 Like
    1. Does UEFI (BIOS) see full RAM?

I hope you saw my second comment after post. I could not say if UEFI (BIOS) [I’m a bit confused here, sorry @ricklinux ] sees full RAM as long as I couldn’t get into it. Now, after everything seems working, RAM is detected correctly (16GB). (I even took a photo

  1. Does Windows 10 see full RAM?

In the past when it happened, yes. Now I didn’t check, but I assume still yes.

So you’re 100% positive it’s only Linux doesn’t see it?

I’ve restarted the system and booted with fallback initramfs. RAM is detected correctly.

hmmm…

Well, for that 100% I think I will have to make a fresh reinstall, reproduce the thing and boot to Windows to check for sure. But I don’t remember to affect windows in any way in the past…so…

1 Like

Personally i’m out of ideas for now…

Return that command, perhaps it will help those who’ll come here to help you as well:

sudo dmidecode -t memory

@anon31687413 maybe there was something funky you recall in Kernel, about this fairly new CPU (Intel Core i7-1065G7) / soldered RAM?


Also usual suspect would be Kingston nvme, that is very bad manufacturer, see this and that

That could be very well a reason, given how random sometimes those failures are, but i don’t think it’s that this time, at least yet. Because if it was - drive would be most likely already dead and you wouldn’t be able to boot.

Well, for the moment I’m happy that it’s working and unless I will do a fresh reinstall I (probably) won’t be affected by this. Even then, I think I have the recipe to solve it fast (as I described in the 2nd comment after post).

Here is the output you asked:

$ sudo dmidecode -t memory

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.

Handle 0x000F, DMI type 16, 23 bytes
Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 16 GB
        Error Information Handle: No Error
        Number Of Devices: 2

Handle 0x0010, DMI type 17, 84 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: No Error
        Total Width: 32 bits
        Data Width: 32 bits
        Size: 8192 MB
        Form Factor: Row Of Chips
        Set: None
        Locator: ChannelA-DIMM0
        Bank Locator: BANK 0
        Type: LPDDR4
        Type Detail: Synchronous
        Speed: 3200 MT/s
        Manufacturer: Samsung
        Serial Number: 20000000
        Asset Tag: 9876543210
        Part Number: K4UBE3D4AA-MGCH     
        Rank: 2
        Configured Memory Speed: 2667 MT/s
        Minimum Voltage: 1.5 V
        Maximum Voltage: 1.5 V
        Configured Voltage: 0.6 V
        Memory Technology: DRAM
        Memory Operating Mode Capability: Volatile memory
        Firmware Version: Not Specified
        Module Manufacturer ID: Bank 1, Hex 0xCE
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: 8 GB
        Cache Size: None
        Logical Size: None

Handle 0x0011, DMI type 17, 84 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: No Error
        Total Width: 32 bits
        Data Width: 32 bits
        Size: 8192 MB
        Form Factor: Row Of Chips
        Set: None
        Locator: ChannelB-DIMM0
        Bank Locator: BANK 2
        Type: LPDDR4
        Type Detail: Synchronous
        Speed: 3200 MT/s
        Manufacturer: Samsung
        Serial Number: 20000000
        Asset Tag: 9876543210
        Part Number: K4UBE3D4AA-MGCH     
        Rank: 2
        Configured Memory Speed: 2667 MT/s
        Minimum Voltage: 1.5 V
        Maximum Voltage: 1.5 V
        Configured Voltage: 0.6 V
        Memory Technology: DRAM
        Memory Operating Mode Capability: Volatile memory
        Firmware Version: Not Specified
        Module Manufacturer ID: Bank 1, Hex 0xCE
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: 8 GB
        Cache Size: None
        Logical Size: None

I don’t understand how you’ve solved it by removing boot entries btw…
And especially why / how it’s started.

Well, whatever works for you :upside_down_face:

P.S. Still i’d check RAM with memtest, just in case.

That is undoubtedly true - but I am not sure it is avoidable! Many manufacturers use the term BIOS for the UEFI firmware, often visibly - and lots of us (that know better) misuse the term too. Perhaps we can call it UEFI BIOS :grin:

2 Likes

GNU / Linux
UEFI / BIOS

That’s how meme got born! :rofl:

P.S. I use Arch btw :rofl:

1 Like

I might have done some terrible things there (if possible) when I struggled with another problem some time ago. I know I look very stupid saying that and I should have more knowledge in this area :laughing:.

Thanks for your time! :+1:

3 Likes

BTW, while am at this, I feel the need to show what’s in my boot manager (got in this by stressing on F12) and UEFI > Boot section (F2).

So in Boot Manager the options are clearly displayed, although only 1 and 3 are needed. I cannot get rid of the rest.

In UEFI > Boot the first 2 options are displayed so wrong (EndeavourOS is the first and it’s displayed as empty, and the second seems to be a very long binary). From 3…6 are displayed ok (even though I didn’t scroll to make another print screen).

In /boot/efi (where is mounted the 100MB-fat32-partition from which initially only Windows10 was booting) I have the following:

➜ sudo ls /boot/efi                
a9ba2b5e37794e03b8baccad6ee26e8b  boot-repair  EFI  loader
~ 
➜ sudo ls /boot/efi/EFI            
Boot  EndeavourOS  GRUB  Insyde  Linux  Microsoft  OEM  systemd  tools  UpdateCapsule
~ 
➜ sudo ls /boot/efi/EFI/Boot       
BOOT.CSV  bootx64.efi  bootx64.efi-1587024234.bak  drivers_x64  fbx64.efi  grub.cfg  grubx64.efi  icons  icons-backup  keys  refind.conf  refind.conf-sample
~ 
➜ sudo ls /boot/efi/EFI/EndeavourOS
grubx64.efi
~ 
➜ sudo ls /boot/efi/EFI/GRUB       
grubx64.efi
~ 
➜ sudo ls /boot/efi/EFI/Insyde
~ 
➜ sudo ls /boot/efi/EFI/Linux 
grubx64.efi
~ 
➜ sudo ls /boot/efi/EFI/Microsoft
Boot  Recovery
~ 
➜ sudo ls /boot/efi/EFI/systemd  
systemd-bootx64.efi
~ 
➜ sudo ls /boot/efi/EFI/tools  
~ 
➜ sudo ls /boot/efi/EFI/OEM  
Boot  Recovery

@devtud
You can use efibootmgr to remove entries

What does efibootmgr show? Can you post the output of:

efibootmgr

I pasted below the output of efibootmgr. As I previously mentioned, even if I remove them with efibootmgr -B -b XXXX, after restart they are displayed again - so they are not actually removed. But, removing them this way it’s essential to solve the issue I opened this post for (I also describe this in the second comment after the post):

So here’s the output you asked for:

➜ efibootmgr 
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000,0006,2001,0004,2002,2003
Boot0000* Linpus lite
Boot0001* BOOTx64.EFI
Boot0002* EndeavourOS
Boot0003* deepinfromubi.efi
Boot0004* deepinpc
Boot0006* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network

its not -B -b xxx the correct way is sudo efibootmgr -b xxxxx -B I know as i used efibootmgr yesterday with 100% success
The lowercase b is the command to modify the entry, the uppercase B then deletes the entry

I guess they are interchangeable as any other named parameters.