Boot stucks at "loading initial ramdisk" after every Update

[CreamyCewie]

Hello my friends,

i recently updated my system, now it´s "stuck" on "loading initial ramdisk" while booting.

As suggested in a few threads here, i tried to load an Pre-Update-Snapshot.
After selecting the snapshot via GRUB garuda loads sucessfully, everything seems to work.
Snapper told me to immediatly reboot, i did this.
After Reboot i only came to grub rescue mode.

As described in another Thread here, i boot from garuda iso and repaired GRUB (via "Garuda Boot Repair" from garuda-welcome).
After that i restarted again and garuda still boots fine.

Then Discover told me that i´ve got (about 340) Updates outstanding, so i installed them.
After this, garuda-maintanence told me that i should perform a full update (partially updates are not supported), wich i did.
After Updating and restarting, i´ve got the same problem again, boot stucks at "loading initial ramdisk".

You´ve got any ideas how to fix this and perform updates again?

greetz
CreamyCewie

[NaN]

Booting and input issues after update

We still don't know if that's your problem, so I suggest that you first test the removed splash on a single boot (not permanent). This should be done when your system is updated, so unbootable, of course. When you are in the grub line that you want to use, press button E, go to the line starting with linux and remove splash, then CTRL+x If it works (you can boot), you can easily set this as permanent with the Garuda Boot Options tool in the Kernel parameters field. Or, at that point, you can …

[CreamyCewie]

Ty, i´ll try this and report you if it helped

[Yaku]

I've had the same issue on both Garuda Xfce and Garuda Dr460nized.
Choosing the repair boot option in the Garuda bootloader gui solved it !

[CreamyCewie]

@Yaku
Repair Boot didnt worked.

As mentioned by @NaN i´ve tried to delete "splash" from GRUB, and now my system booted normally again.

Problem seems to be solved through this.

Just for my knowledge, any Idea why "splash" made a problem?
Don´t want it to happen again

greetz
CreamyCewie

[NaN]

The latest plymouth-git update has a bug. That’s why removing the splash kernel parameter disabled plymouth’s execution and allowed you to boot normally,
You can resolve this by going from plymouth-git to plymouth. The reason why garuda uses plymouth-git by default is because the “regular” plymouth package doesn’t receive updates as often.

To switch the packages:

sudo pacman -S plymouth

This will ask you to remove plymouth-git since it conflicts with plymouth enter Y to do so and continue installing. After the installation is done to update the initramfs follow the post below, It’s necessary for plymouth.

System wont start after update

The splash parameter is for plymouth. Did you rebuild your initramfs after changing from plymouth-git to plymouth? I am asking because I have plymouth installed and updated my system yesterday and haven't faced this issue at all. List all available themes in plymouth plymouth-set-default-theme -l which should give something like this bgrt details dr460nized fade-in glow script solar spinfinity spinner text tribar The default for KDE dr460nized is dr460nized set it as plymouth's theme: su…

[heinrikur]

I had the same issue, but none of my snapshots or even the repair option was working. Got stuck at a black screen only showing Setup Virtual Console failed to load. I reinstalled before I saw the thread here on the forum.