It’s kind of buggy where I’ll enter characters but they won’t register. I can verify this because when booting, sometimes my num and caps lock keys will have a delay after pressing before their light changes.
This is very annoying when trying to unlock the computer, because I essentially have to wait an arbitrary amount of time before I think inputs will register properly. This wouldn’t be as much of an issue if I could, you know, get some feedback that they keys I’m entering are actually being entered.
Is there a way to change this to suit my needs better?
By default, Fedora shows the per-character dots. It’s probably something in plymouth.
In whatever centos uses for a prompt, it says “press tab for echo”, and it works. You’ll need to provide more info about your environment if you don’t have that option.
You may want to check out openSUSE. It does this on a system where
/is encrypted but/bootis not.I changed my mkinitcpio hook from the busybox init
encryptto systemd initsd-encryptto help with this, as it presents a different way to unlock a LUKS partition. Be sure to read the notes aboutsd-vconsoleif you use this hook. Your mileage may vary since im not sure which OS you’re on.Perhaps this is a little overkill, but you could install a display manager like GDM or SDDM that displays a graphical password input.
They’re asking about the password prompt for the disk encryption, which is shown before the rootfs can be accessed. Thus, installing a display manager to the rootfs will not help. Furthermore, a display manager serves the purpose of logging in users, not unlocking an encrypted partition.
You are right! I meant to refer to Plymouth, which will do what I described. It’s been a while since I did this.
