[SOLVED] Problems with Plymouth and dm-crypt

mcComBat · 2016-03-18 16:51:17

Hello everyone,
I've just installed Plymouth and followed every instruction I could find on how to make it work properly with an encrypted system.
Yet, for some reason, the moment my system starts boot, I see the Plymouth GUI winch asks for the dm-crypt password, but it doesn't really accept any password -
When the screen is shown, I'm pretty sure I see a mouse for a brief moment, and then after it disappears, there is a blinking cursor (top left of the screen) and it "overwrites" the GUI screen, I can type stuff but nothing reacts to it.

If I interrupt the boot process and and remove the splash option, I can boot using a text prompt (I assume there is some kind of fallback in Plymouth).

I'd be really happy if you guys could help me make this work.
Thanks!

My boot entry:

title	Arch Linux
linux	/vmlinuz-linux
initrd  /intel-ucode.img
initrd	/initramfs-linux.img
options	cryptdevice=/dev/sdb2:luks-vgcrypt quiet splash root=/dev/vgcrypt/root rw

My 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="ext4"

# 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 autodetect plymouth plymouth-encrypt modconf block lvm2 filesystems keyboard 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_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Last edited by mcComBat (2016-03-18 23:59:43)

mcComBat · 2016-03-18 23:58:58

Solved by using plymouth-git instead of plymouth from the AUR - compiling the newest version.

Last edited by mcComBat (2016-03-18 23:59:25)

MaddyBoo · 2017-05-02 05:49:38

mcComBat wrote:

Solved by using plymouth-git instead of plymouth from the AUR - compiling the newest version.

I know this thread is quite old, but I wanted to say that this worked for me too.

Seems odd to me that whatever fixed this bug hasn't been merged into the main Plymouth repo yet, over a year later.

WorMzy · 2017-05-02 06:20:16

Please don't necrobump, MaddyBoo.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Arch Linux

#1 2016-03-18 16:51:17

[SOLVED] Problems with Plymouth and dm-crypt

#2 2016-03-18 23:58:58

Re: [SOLVED] Problems with Plymouth and dm-crypt

#3 2017-05-02 05:49:38

Re: [SOLVED] Problems with Plymouth and dm-crypt

#4 2017-05-02 06:20:16

Re: [SOLVED] Problems with Plymouth and dm-crypt

Board footer