Bug 18495

Description of problem:

§ Unlocking encryption in texmode boot fail

§ Needing to rely on graphic modes working for unlocking encryption of the system is low reliability.


This problem do *NOT* show an a similar setup where i did a *fresh* install of mga6 64bit, but that it was a couple weeks ago.  I do not wish to tinker with that one or update it. Kernel there is 4.6.0-desktop-0.rc7.3.mga6. (On that system i can open LUKS in text as well as in graphics boot mode) 

So I can not say if problem is because of newer versions of something, or because of some migration bug.

The problematic system was fresh installed mga5 64 bit.
/, /swap and /home is on an encrypted LVM, /boot on normal sda1 ext4
Two days ago upgraded online to mga6 Cauldron, and problem persist after updates today.  (i.e kernel is 4.6.0-desktop-1.mga6 )

What happens during boot if booting in text mode:


1) It stops *) to ask for encryption key.

*) it have written maybe twenty lines of more messages after it printed the question and it do not show any cursor - A variant of Wontfix Bug 5408

2) for every keypress it tries to evaluate the key, find it is wrong and ask again.

3) after four keypresses no more tries and encryption can not be unlocked.



Steps to Reproduce:
1. Have an encrypted mga5 system that boots in text mode
2. upgrade online
3. at reboot you can not unlock

WORKAROUND
At boot edit kernel parameters so you get graphical boot
(default on an new install but as i have had problems with that before more than graphical, i have changed to textmode)
- The graphical dialog for entering luks key works