Stuck on loading initial ramdisk after update

Issues & Assistance Newbies
1

inxi before update:

System:
  Kernel: 5.19.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=21c7fde8-1bef-4f82-abc8-364dad2d6848 rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=59131e58-a432-49f0-bae1-aebf3325230e loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.25.4 tk: Qt v: 5.15.5 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: OMEN by HP Laptop 15-dc1xxx v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 8574 v: 21.17 serial: <superuser required> UEFI: AMI
    v: F.22 date: 05/03/2021
Battery:
  ID-1: BAT0 charge: 45.8 Wh (100.0%) condition: 45.8/45.8 Wh (100.0%)
    volts: 17.4 min: 15.4 model: HP Primary type: Li-ion serial: N/A
    status: full
CPU:
  Info: model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 9 built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158)
    stepping: 0xD (13) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1850 high: 2600 min/max: 800/4500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1100 2: 2600 3: 2600
    4: 1100 5: 1101 6: 2600 7: 1100 8: 1100 9: 2600 10: 2600 11: 2600
    12: 1100 bogomips: 62399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  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: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard
    driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-07) arch: Turing code: TUxxx
    process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1f11 class-ID: 0300
  Device-2: Lite-On HP Wide Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 1-6:3 chip-ID: 04ca:707f class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
    compositors: 1: kwin_x11 2: Tabby driver: X: loaded: nvidia gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.43x7.52")
    s-diag: 391mm (15.39")
  Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 142
    size: 344x194mm (13.54x7.64") diag: 395mm (15.55") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA
    515.65.01 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA TU106 High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Sound Server-1: ALSA v: k5.19.2-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 3d:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: br-da2c536dbf10 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-7:4 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 5020 bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
Drives:
  Local Storage: total: 1.84 TiB used: 62.46 GiB (3.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB1T0HBLR-000H1 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: HPS0NEXF temp: 45.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46 GiB
    (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 563 KiB
    (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46 GiB
    (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46
    GiB (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46
    GiB (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.23 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.36 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 83.0 C pch: 54.0 C mobo: N/A gpu: nvidia
    temp: 55 C
  Fan Speeds (RPM): cpu: 2393 fan-2: 2207
Info:
  Processes: 338 Uptime: 4m wakeups: 1 Memory: 31.23 GiB used: 4.03 GiB
  (12.9%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 Packages: pacman: 1687 lib: 498 Shell: fish v: 3.5.1
  running-in: tabby inxi: 3.3.20
Garuda (2.6.6-1):
  System install date:     2021-07-24
  Last full system update: 2022-08-20
  Is partially upgraded:   No
  Relevant software:       tlp NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Timeshift (maybe)
  Failed units:

Hello everyone,

I am unable to update my system. After update which succeeds without any errors when I reboot the system it gets stuck on loading initial ramdisk. I've waited for about 30 minutes and nothing changed. I was able to revert to previously working snapshot before the update without problems, but this means I cannot install any new software before this issue gets resolved. I am unable to perform inxi after the update because I can't get into the system (or I lack the necessary know-how to do so).

I used 'sudo garuda-update -a' to update my system.

Thanks in advance for any help.

2

Do you use

garuda-update -a

???

1 Like
3

Yes, of course. Everytime I update my system I use

sudo garuda-update -a

So far it worked without any problems. As you can see from inxi I update my system regularly.

4

You know that, so please, tell that :slight_smile: in OP.

mem_encrypt=off

Do you use encryption?

Did you search the web?

2 Likes
5

Sorry, will mention this if this happens in the future.

No, I don't use encryption, I've installed Garuda Linux normally using btrfs. I was thinking about disk encryption, but I came to realize that then I probably won't be able to use btrfs because it forced me to use LUKS, so I've abandoned this idea and I'm storing sensitive info in veracrypt encrypted volumes.

6

This probably means the initramfs didn't build correctly. Watch the output from updates carefully, and when you're in the system (e.g. chroot or using an alternative kernel) run mkinitcpio -P and see what the output says.

3 Likes
7

This is the output of mkinitcpio -P after update:

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'

-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img

==> ERROR: Unable to write to /boot/initramfs-linux-zen.img

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'

-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect

==> ERROR: Unable to write to /boot/initramfs-linux-zen-fallback.img
8

Looks like DKMS itself is broken:

Flyspray, a Bug Tracking System written in PHP.

Install regular linux kernel and the precompiled driver for it:

sudo pacman -S linux linux-headers nvidia

then reboot and choose "linux" kernel, not "linux-zen"

2 Likes
9

Well,

that did the trick for now. Thanks!

1 Like
10

I hope Arch Linux devs timely fix the bug and Garuda devs implment a workaround before this becomes widespread.

1 Like
11

We have your fix :smiley:

2 Likes
12

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