Stuck at “Loading initial ramdisk ...”

Hi folks,

I know that this thread may have been posted a dozen times already, but I’m looking on how to fix it with no avail.

Here is what I have tried so far:

  • Updated my BIOS to the latest version
  • Chroot and run pacman -Syu
  • Run mkinitcpio -P under chroot
  • Run pacstrap from the live USB and resintall a few packages

My system:

  • AMD Ryzen 1400
  • Mobo Asus B350m
  • Nvidia 1050ti

Please guide on what I should try next. Thank you for your time.

1 Like

If you have installed EnOS with the default configuration of the installer, then mkinitcpio is not used as initramfs generator.

EnOS uses dracut by default.


You could try chrooting into your system (use the method appropritae for your filesystem).

Inside the chroot run:

reinstall-kernels (if using systemd-boot)


dracut-rebuild (if using Grub)

1 Like

Thank you for the fast response,

Seems that I don’t have installed resintall-kernel nor dracut-rebuild. Forgot to add that I installed eOS around October 2022. Seems that I’m using mkinitcpio because I have a config file on /etc, and I dont have /etc/dracut.conf.d.

You think installing dracut may help?

Could you post the output of the following commands from the live session?

sudo parted -l
1 Like

Sure friend,

I have a dual boot system with Windows 10

1 Like

Perhaps you could try to chroot again:

sudo mount /dev/sda5 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
sudo arch-chroot /mnt

Inside chroot, try reinstalling your kernels:

pacman -Syu linux linux-headers (for example for the latest stable)

This should trigger mkinitcpio automatically.

Check under /boot directory to see if the kernel images and the initramfs are present.

For good measure, reinstall the bootloader and regenerate your grub.cfg:


grub-mkconfig -o /boot/grub/grub.cfg

When done, type exit followed by enter to quit chroot.


1 Like

A typo with the command, should be


Good catch! :eye:

However, looking at the output provided, the OP is using the good old EXT4-Grub combo so reinstall-kernels is out of the equation.


Yeah, thanks, missed that. :upside_down_face:



Here is what I did:

  • Downgraded to the previous kernel version I had on cache
  • Grub reinstall and make config as your comment says

Seems that the latest kernel may have an issue with my system. I will update and carefully look at the logs next time!

1 Like

Great! Glad you got it it resoved!

Perhaps you could consider linux-lts in the meantime if you are experiencing issues with the latest stable?

1 Like

Just started to suggest the LTS kernel too. :wink:

1 Like

The LTS kernel is a good idea to have too. Can save some extra work.

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