Plymouth - plain encrypt message instead of graphical during boot

AdisonCavani · 2021-01-31 00:23:05

Hi, I'm experiencing problems with Plymouth. Boot process should look like this: GRUB menu -> graphical Plymouth encryption prompt -> GDM, but it look: GRUB menu -> "A password is required to access..." (plain terminal text), then after few seconds Plymouth animation with password prompt appears -> GDM

According to Plymouth wiki page I've set my HOOKS in mkinitcpio.conf like this:

HOOKS=(base udev plymouth autodetect keyboard keymap modconf block plymouth-encrypt filesystems fsck)

I've got a "loglevel=0" in grub file, because it's hiding annoying message during boot: "[...] No irq handler for vector". There is a thread on this forum, but I didn't found other solution for this.

What is causing this problem and how to solve this?

Here are my files:

/etc/mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()
 
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
 
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()
 
# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev plymouth autodetect keyboard keymap modconf block plymouth-encrypt filesystems fsck)
 
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"
 
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

/etc/default/grub:

# GRUB boot loader configuration
 
GRUB_DEFAULT="Windows 10"
GRUB_TIMEOUT="15"
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash loglevel=0 vga=current rd.udev.log_priority=3 vt.global_cursor_default=0"
GRUB_CMDLINE_LINUX="cryptdevice=UUID=058ef897-c997-49c6-be9e-a79795dda3e1:cryptroot root=/dev/mapper/cryptroot"
 
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
 
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK="y"
 
# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE="menu"
 
# Uncomment to use basic console
GRUB_TERMINAL_INPUT="console"
 
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT="console"
 
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE="1920x1080"
 
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX="keep"
 
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID="true"
 
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"
 
# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
 
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME="/boot/grub/themes/Vimix/theme.txt"
 
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
 
# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT="false"

/etc/plymouth/plymouthd.conf

# Distribution defaults. Changes to this file will get overwritten during
# upgrades.
[Daemon]
Theme=deus_ex
ShowDelay=0
DeviceTimeout=8

QuixoticBite · 2021-01-31 01:43:08

I haven't used Plymouth in a while, and I haven't used it in Arch at all, but I'll try to help:

~~Try moving the `plymouth-encrypt` hook to right after `plymouth` in mkinitcpio.conf per the warning in the documentation.~~ - edit: Per Slithery's post, this does not apply.

edit: There's also a note right underneath that might apply to you:

After adding the plymouth-encrypt hook, if input goes to the background in plaintext instead of into the password prompt you need to add your (kernel) graphics driver to your initramfs.

Make sure to renegerate your initramfs afterwards.

Last edited by QuixoticBite (2021-01-31 02:04:45)

Slithery · 2021-01-31 01:57:29

QuixoticBite wrote:

Try moving the `plymouth-encrypt` hook to right after `plymouth` in mkinitcpio.conf per the warning in the documentation.

That isn't what the warning tells you to do, in fact it will never work if you do that. You have to have the encrypt hook after the block hook otherwise there are no devices available to unlock.

AdisonCavani · 2021-02-01 12:57:27

I installed LTS kernel and everything is OK. This might be an issue with latest 5.10 kernel.

Arch Linux

#1 2021-01-31 00:23:05

Plymouth - plain encrypt message instead of graphical during boot

#2 2021-01-31 01:43:08

Re: Plymouth - plain encrypt message instead of graphical during boot

#3 2021-01-31 01:57:29

Re: Plymouth - plain encrypt message instead of graphical during boot

#4 2021-02-01 12:57:27

Re: Plymouth - plain encrypt message instead of graphical during boot

Board footer