You are not logged in.
Pages: 1
I recently decided to try plymouth (sddm-plymouth) when booting my luks container. (/boot is unencrypted). I followed the wiki.
I get a nice graphical password prompt, then as the rest of the initramfs works, the display flickers back to a verbose boot screen, then back to graphical again. the process is very choppy.
my mkinitcpio hooks are:
HOOKS=(base udev autodetect keyboard modconf block plymouth plymouth-encrypt filesystems resume)modules are:
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm btrfs)my grub parameters are:
GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=/dev/nvme0n1p3:cryptssd:allow-discards intel_iommu=on iommu=pt nvidia-drm.modeset=1 rootflags=subvol=@rootfs resume=UUID=679deacb-1335-4a4f-9056-e3310caffd8f loglevel=3 udev.log_level=3 fbcon=nodefer quiet splash"I read this flicker may be due to the nvidia graphics. am I doing something in this setup which might be causing the issue?
thanks.
Offline
According to the plymouth wiki, you should put plymouth after (base udev...) in the hooks and that might improve it.
There is not much you can do with plymouth except for what is already in the wiki as it runs really early in the boot process for any user control.
Offline
I'm still learning about the hooks. Should the plymouth-encrypt hook come immediately after that?
Offline
Read the Warning part of the wiki. It does say to put it after the plymouth hook (base, udev, plymouth, plymouth-enctypt...)
Offline
I know it must come after. *Immediately* after is what I'm curious about, since that's not how I've had it.
Offline
Pages: 1