Error during boot

Issues & Assistance KDE
1

Hey guys.

I recently did a clean reinstall of Garuda, but every time I boot my system I get this error. When I press enter it continues normally unto the login screen. No issues.

Any idea why it's doing this? Inxi below...

IMG_20221018_183537
IMG_20221018_1835371139×887 64.4 KB 

╭─[email protected] in ~
╰─λ garuda-inxi
System:
Kernel: 6.0.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3f3caa78-25e6-4ffe-afd3-f0a03399596d rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=5e5fd313-a563-4aac-8967-381f0cac22ea loglevel=3
Desktop: KDE Plasma v: 5.26.1 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK (MS-7C02) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.I0
date: 07/25/2022
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101016
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 3500 min/max: 1600/3500 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500 3: 3500
4: 3500 bogomips: 27948
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT disabled
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands
process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 ports: active: DVI-D-1 empty: DP-1,DVI-D-2,HDMI-A-1
bus-ID: 10:00.0 chip-ID: 1002:67df class-ID: 0300 temp: 51.0 C
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
s-diag: 485mm (19.11")
Monitor-1: DVI-D-1 mapped: DVI-D-0 model: Samsung SyncMaster
serial: <filter> built: 2009 res: 1600x900 hz: 60 dpi: 92 gamma: 1.2
size: 443x250mm (17.44x9.84") diag: 509mm (20") ratio: 16:9 modes:
max: 1600x900 min: 720x400
OpenGL: renderer: AMD Radeon RX 570 Series (polaris10 LLVM 14.0.6 DRM
3.48 6.0.2-zen1-1-zen) v: 4.6 Mesa 22.2.1 direct render: Yes
Audio:
Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 link-max: lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:aaf0
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 30:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound API: ALSA v: k6.0.2-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: down mac: <filter>
IF-ID-1: enp18s0f0u9 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
Device-1: T & A Mobile Phones VFD type: USB driver: rndis_host v: kernel
bus-ID: 1-9:5 chip-ID: 1bbb:0174 class-ID: 0a00 serial: <filter>
Report: bt-service: enabled,stopped note: tool can't run
Drives:
Local Storage: total: 2.05 TiB used: 17.7 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Mushkin model: MKNSSDHL250GB-D8
size: 232.89 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: S1111A0L
temp: 47.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 1U scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Toshiba model: MQ01ABD100
size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: HDD
rpm: 5400 serial: <filter> scheme: MBR
Partition:
ID-1: / raw-size: 223.79 GiB size: 223.79 GiB (100.00%) used: 17.7 GiB
(7.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB
(0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 223.79 GiB size: 223.79 GiB (100.00%) used: 17.7
GiB (7.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 223.79 GiB size: 223.79 GiB (100.00%) used: 17.7
GiB (7.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 223.79 GiB size: 223.79 GiB (100.00%) used: 17.7
GiB (7.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.68 GiB used: 1024 KiB (0.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 47.6 C mobo: N/A gpu: amdgpu temp: 51.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 1246
Info:
Processes: 251 Uptime: 7m wakeups: 0 Memory: 7.68 GiB used: 2.46 GiB
(32.0%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1476 libs: 480
tools: gnome-software,octopi,paru Shell: fish v: 3.5.1 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-10-17
Last full system update: 2022-10-18
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:            systemd-vconsole-setup.service

╭─[email protected] in ~ took 1s
╰─λ
2

You may still have an old UEFI boot entry. Check the output of efibootmgr. Delete the old entry with sudo efibootmgr -Bb 0000, substituting 0000 for the entry you would like to remove.

If you aren't sure which one you are supposed to keep and which one you should get rid of, you can delete them all (assuming you are not dual-booting) and set up a new one by running grub-install.

3

A prime example of images the world doesn't need.

If someone is looking for the solution to this message,

error: out of memory.

he will not find it.
Because it is not in the headline nor in the help request.

2 Likes
4

Honestly, I would much rather see a photo of this specific issue than "I have error out of memory pls halp"

5

Strange. There were various people complaining about that issue (same time as the Grub no boot disaster ^^) but it should be fixed.

My suggestion would be to boot garuda-install-medium, chroot into installation and reinstall Grub.

There's clearly enough space on the UEFI-partition.

Also read of people having this issue while using Grub-themes and being able to fix it by just commenting the GRUB_THEME= line in /etc/default/grub

So I'd try those two and if they yield no results report back.

1 Like
6

The OP can boot into the system, so this is a little more work than is necessary--running grub-install is all that is needed.

I believe this is not related to Grub at all, but rather related to the UEFI boot entries. When everyone was reinstalling Grub from the bug, some folks would up with old UEFI boot entries still stuck as the default.

7

First boot order does seem to be Garuda. Is this correct? I'm not so technical oriented.

╭─[email protected] in ~
╰─λ efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,000A,0001,000B
Boot0000* Garuda        HD(1,GPT,a17e3fd1-a02c-ea4b-b183-c8c58c499304,0x1000,0x96000)/File(\EFI\GARUDA\GRUBX64.EFI)
Boot0001* Hard Drive    BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc3000000010000008b0054004f005300480049004200410020004d005100300031004100420044003100300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600020101010600010003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000200020002000590020004e00340050003700410043005400300000007fff04000000424f00004e4fbf000000010000008b004d004b004e0053005300440048004c00320035003000470042002d00440038000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a00000000010106000601010106000000031710000100000000000000000000007fff040001043800ef47642dc93ba041ac194d51d01b4ce64d004b0032003000300036003200360031003000300036003800350033004300370000007fff04000000424f
Boot000A* UEFI OS       HD(1,GPT,a17e3fd1-a02c-ea4b-b183-c8c58c499304,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot000B* USB HDD       BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)0000474f00004e4fc1000000010000007b0054004f00530048004900420041002000450078007400650072006e0061006c002000550053004200200033002e00300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060002010101060000000305060003007fff040001043200ef47642dc93ba041ac194d51d01b4ce63200300031003700300039003200380030003200300032003100370000007fff04000000424f
8

That does look right, but unless you are multibooting you do appear to have old/unneeded boot entries.

If this is the only OS on the system, I would start fresh by deleting them all, then run grub-install which will automatically create a new one based on your current configuration.

9

I installed from a 220822 Talon ISO, perhaps this ISO didn't have the fix?

220822 is probably the date code of release of the ISO?

EDIT: I did the following. Restarted, still gives the Error: out of memory message. Still boots fine after pressing enter.

Screenshot_3
Screenshot_31600×900 171 KB

10

Oops, try running with sudo:

sudo grub-install

Please paste terminal output as text whenever you can (not screenshots).

3 Likes
11

Error is gone.

Strange, GRUB looks different now, it was all black with text. Now after running sudo grub-install command it's colorful like the rest of Garuda.

Thank you for everyone's assistance.

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.