CachyOS stuck on loop

[Xanar]

Whenever I boot up CachyOS, I (sometimes) get stuck on this screen. All I see is a spinning circle. I can’t do anything (CTRL+ALT+FX) or so. Only reboot using CTRL+ALT+DEL

I don’t know why that’s happening. I hope someone can help me.

[cscs]

Hello and welcome,

You can disable the boot splash to at least see whats happening;

[Tutorial] Disable or Remove Plymouth (boot splash)

Introduction CachyOS ISOs provide and enable plymouth by default. From the ArchWiki: Which is to say it is not a system-critical component.* It also has a nasty habit of breaking boot under various circumstances. In those cases, or simply to avoid the bloat, you can temporarily disable plymouth, permanently disable it, or remove it entirely. * - Some systems use Plymouth to forward decryption prompts. This may be especially useful in cases where the language and input devices might differ.…

And for general system info and the like we could do this:

sudo cachyos-bugreport.sh

[Xanar]

Removing the “splash” thingie instantly boots up to KDE. 3 tries, 3 success. Could it be that Playmouth is buggy?

[cscs]

I mean .. I think it is.
Theres lots of anecdotal posts of it not working right and/or breaking boot under different conditions.
It might be fixable if you apply early-KMS or something else.
But to me it is at best an unnecessary process/animation that can only slow down your boot and hide information. When it is working perfectly. So I banish it on my systems.

[Xanar]

I disabled it completely in my grub and let’s hope that my issues are now fixed. I mean I wouldn’t be able to see the fancy splash anyway because around that time my other monitor turns on, causing both monitors to refresh

[pgnonick]

Hey everybody,
i had the same exact issue. And thx for the workaround. After removing splash it is normally booting.

I send out also the bug report. But what I can report is, that the issue appears after setup secure boot. I added the packman system hook, for sbctl auto signing if boot manager or kernel updates were applied. Then booting into system was only possible in really rare moments. So I think this hook and Plymouth in combination results for me into this endless loop.