[Bug 825744] New: plymouth: Unable to unlock the encrypted volume when booting Dom0 as the keyboard isn't working at this stage
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c0 Summary: plymouth: Unable to unlock the encrypted volume when booting Dom0 as the keyboard isn't working at this stage Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: nick.couchman@seakr.com QAContact: jsrain@suse.com CC: jbeulich@suse.com, ohering@suse.com, joop.boonen@boonen.org, nick.couchman@seakr.com, novell-ugeuder@sneakemail.com Depends on: 775669 Found By: Community User Blocker: --- +++ 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c1 --- Comment #1 from Nick Couchman <nick.couchman@seakr.com> 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |Basesystem AssignedTo|jsrain@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |tittiatcoke@gmail.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c2 --- Comment #2 from Raymond Wooninck <tittiatcoke@gmail.com> 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c3 --- Comment #3 from Nick Couchman <nick.couchman@seakr.com> 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? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c4 --- Comment #4 from Raymond Wooninck <tittiatcoke@gmail.com> 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). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c5 --- Comment #5 from Nick Couchman <nick.couchman@seakr.com> 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tittiatcoke@gmail.com |kigurame@opensuse.org -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c6 Bug 825744 depends on bug 775669, which changed state. Bug 775669 Summary: plymouth: Unable to unlock the encrypted volume when booting Dom0 as the keyboard isn't working at this stage http://bugzilla.novell.com/show_bug.cgi?id=775669 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #6 from Raymond Wooninck <tittiatcoke@gmail.com> 2014-02-07 09:01:51 UTC --- *** Bug 775669 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=775669 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825744 https://bugzilla.novell.com/show_bug.cgi?id=825744#c7 --- Comment #7 from Uwe Geuder <novell-ugeuder@sneakemail.com> 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... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com