Polished single-user booting or heavy lifting with Plymouth

[vini.nu]

Currently done changes to default installation:

Manually created mkdir -P /usr/lib/dracut/modules.d/50numlock and added script from this repo:

GitHub - FivEawE/dracut-numlock: A dracut module which enables numlock in the...

and

# chmod 755 /usr/lib/dracut/modules.d/50numlock/module-setup.sh
# chmod 755 /usr/lib/dracut/modules.d/50numlock/numlock.sh
# dracut-rebuild

---

Contents of /etc/kernel/cmdline (actually one line; I split it here for convenience only):

quiet
splash
loglevel=3
systemd.show_status=auto
rd.udev.log_level=3
vt.global_cursor_default=0
nvidia-drm.modeset=1
nvme_load=YES
nowatchdog
rw
rootflags=subvol=/@
rd.luks.uuid=be76895b-b4ed-4cb7-b5e1-987f3022c404
root=/dev/mapper/luks-be76895b-b4ed-4cb7-b5e1-987f3022c404
nvidia_drm.modeset=1

---

Plymouth theme install and set:

$ yay -S plymouth-theme-bgrt-better-luks
# plymouth-set-default-theme bgrt-better-luks

Modified dracut configs:

$ ls -a /etc/dracut.conf.d
calamares-luks.conf  eos-defaults.conf  plymouth-crypt-unlocking.conf  resume-from-hibernate.conf

$ cat /etc/dracut.conf.d/calamares-luks.conf 
# Configuration file automatically written by the Calamares system installer
# (This file is written once at install time and should be safe to edit.)
# Enables support for LUKS full disk encryption with single sign on from GRUB.

# force installing /etc/crypttab even if hostonly="no"

#install_items+=" /etc/crypttab "

$ cat /etc/dracut.conf.d/eos-defaults.conf 
omit_dracutmodules+=" network cifs nfs nbd brltty "
compress="zstd"

$ cat /etc/dracut.conf.d/plymouth-crypt-unlocking.conf 
add_dracutmodules+=" plymouth crypt "

$ cat /etc/dracut.conf.d/resume-from-hibernate.conf 
add_dracutmodules+=" resume "

and runned dracut-rebuild of course.

---

Plymouth-quit masking:

sudo systemctl mask plymouth-quit.service

---

---

Sauce list:
https://discovery.endeavouros.com/installation/dracut/2022/12/
https://discovery.endeavouros.com/encrypted-installation/encrypted-installation/2021/03/

Numlock on early stage

This should work if you are indeed using mkinitcpio and if you have regenerated your initramfs after doing this. Maybe you forgot to regenerate your initramfs after you changed the configuration, though I could be mistaken and something else is going on. The dates of the files say they were last modified on 21 August. When did you attempt this? Was the attempt made a few days ago? Or is it today?

https://wiki.archlinux.org/title/Plymouth
https://wiki.archlinux.org/title/Systemd#Drop-in_files
https://wiki.archlinux.org/title/Dracut
https://wiki.archlinux.org/title/Silent_boot
https://wiki.archlinux.org/title/Systemd-boot
https://www.reddit.com/r/archlinux/comments/16uzy40/fulldisk_encryption_and_plymouth/

How do I make plymouth work on my system?

You probably need to load you gpu drivers earlier. There is an example of how to do this in the EOS wiki page for dracut. To rebuild your boot images after changibg the config run: sudo dracut-rebuild

https://wiki.archlinux.org/title/Activating_numlock_on_bootup#SDDM

Double entry needed for encryption password

If you use systemd-boot and a swap partition you will need to enter the encryption password twice because storing a keyfile in the initramfs is not practical. An easy way to avoid having to enter the password twice would be to remove the swap partition and instead use a swap file, which will be located inside the encrypted partition. This came up recently in another thread if you are interested in reading through it:

https://discovery.endeavouros.com/nvidia/new-nvidia-driver-installer-nvidia-inst/2022/03/