Bug 825744

Summary:	plymouth: Unable to unlock the encrypted volume when booting Dom0 as the keyboard isn't working at this stage
Product:	[openSUSE] openSUSE 12.3	Reporter:	Forgotten User ToNzP6iHCC <forgotten_ToNzP6iHCC>
Component:	Basesystem	Assignee:	Mark van Tinteren <kigurame>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	forgotten_ToNzP6iHCC, joop.boonen, novell-ugeuder, ohering
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.3
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	775669
Bug Blocks:

Description Forgotten User ToNzP6iHCC 2013-06-19 11:38:04 UTC

+++ This bug was initially created as a clone of Bug #775669 +++

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1

I've installed a brand new openSUSE 12.3 system, including an encrypted volume for /home.

When I boot normally i.e. without Xen i can unlock the encrypted volume. 
When I boot Xen I'm not able to unlock the encrypted volume.  The keyboard is working - at least, Ctrl-Alt-Delete works, but the system doesn't seem to actually be listening for a password for the encrypted volume, as typing and hitting "Enter" do not actually result in an attempt to unlock the encrypted volume.

The device is a Dell Latitude E5430.

Reproducible: Always

Steps to Reproduce:
1.Boot Xen openSUSE 12.3
2.The encryption password is requested
3.The password cant be typed in. Also no reaction on just enter.

Actual Results:  
Cant decrypt the encrypted volume .i.e. openSUSE Dom0 boots, but times out trying to mount /home, and the result is that /home is not mounted.

Expected Results:  
To able to type te password, so openSUSE Dom0 will boot normally and the encrypted volume will be mounted.

Comment 1 Forgotten User ToNzP6iHCC 2013-06-19 11:39:51 UTC

Have also tried uninstalled Plymouth altogether, setting "splash=verbose" and "splash=0", and "rd.plymouth=0", and none of these help.  Booting the default kernel results in the splash screen being displayed, and the prompt actually being able to be entered.

Comment 2 Forgotten User sM9JzehKpy 2013-07-15 15:54:28 UTC

Removing plymouth and not rebuilding the initrd file will not work. The kernel image contains the plymouth binaries in order to be able to boot with the splash. 

So the procedure should be to remove Plymouth and then to rebuild the initrd file with mkinitrd.

Comment 3 Forgotten User ToNzP6iHCC 2013-07-15 16:18:19 UTC

(In reply to comment #2)
> Removing plymouth and not rebuilding the initrd file will not work. The kernel
> image contains the plymouth binaries in order to be able to boot with the
> splash. 
> 
> So the procedure should be to remove Plymouth and then to rebuild the initrd
> file with mkinitrd.

I'm pretty sure I tried this and it still didn't work - I think I did those steps in that order, too - remove Plymouth and rebuild initrd.  Seems like I still ran into issues with the kernel not recognizing the keyboard input at this time.  Maybe not a Plymouth issue - maybe something else?

Comment 4 Forgotten User sM9JzehKpy 2013-07-15 16:25:15 UTC

When you boot this new initrd, do you see a graphical splash or just the kernel and systemd messages flying over the console ? 

If you still see a splash screen, then something went wrong with removing Plymouth. Make sure that you remove all plymouth related files (including libply2, etc).

Comment 5 Forgotten User ToNzP6iHCC 2013-07-15 17:05:23 UTC

(In reply to comment #4)
> When you boot this new initrd, do you see a graphical splash or just the kernel
> and systemd messages flying over the console ? 
> 
> If you still see a splash screen, then something went wrong with removing
> Plymouth. Make sure that you remove all plymouth related files (including
> libply2, etc).

No, no graphical splash screen - just kernel/systemd messages.  It would get to the text-based prompt for the encrypted volume, but never recognize keystrokes.

Comment 6 Forgotten User sM9JzehKpy 2014-02-07 09:01:51 UTC

*** Bug 775669 has been marked as a duplicate of this bug. ***

Comment 7 Uwe Geuder 2014-02-11 11:21:12 UTC

Unlocking of encrypted volume in Dom0 works currently in 13.1

Because of work-around for https://bugzilla.novell.com/show_bug.cgi?id=834063
password is asked in text console. 

Hopefully it doesn't break again when plymouth is back...

Comment 8 Olaf Hering 2015-06-19 13:56:58 UTC

12.3 is not maintained anymore.