[Bug 1047225] New: LUKS password doesn't show up when booting with nomodeset
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Bug ID: 1047225 Summary: LUKS password doesn't show up when booting with nomodeset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: tiwai@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Install a TW system with the standard procedure for LVM+encrpption as suggested by installer on KVM. It works fine with the graphical LUKS password. But when you boot with nomodeset boot option, the boot process hangs without asking the LUKS password. This didn't happen on openSUSE Leap 42.2 / 42.3. And when I upgrade only plymouth packages on the Leap system, it starts showing the same problem. So, it's a regression in the recent plymouth package. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c1 --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- The bug was inspired by another bug report, bug 1020283, BTW. I just wanted to check the behavior, then hit this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sreeves@suse.com Assignee|bnc-team-screening@forge.pr |qzhao@suse.com |ovo.novell.com | --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Reassigned to plmyouth maintainer. Also adding Scott to Cc as backup. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c5 --- Comment #5 from Stefan Dirsch <sndirsch@suse.com> --- Same issue after installing NVIDIA drivers (boo#1053811), although NVIDIA supports KMS meanwhile (/dev/dri/card0 being used by Xserver). So basically every customer using NVIDIA driver on a LVM/Encrypt setup is affected by that issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|LUKS password doesn't show |LUKS password doesn't show |up when booting with |up when booting with |nomodeset |nomodeset or using NVIDIA | |driver -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c6 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyginnovations@gmail.com --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- *** Bug 1053811 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c8 --- Comment #8 from Zhao Qiang 赵强 <qzhao@suse.com> --- (In reply to Stefan Dirsch from comment #5)
Same issue after installing NVIDIA drivers (boo#1053811), although NVIDIA supports KMS meanwhile (/dev/dri/card0 being used by Xserver). So basically every customer using NVIDIA driver on a LVM/Encrypt setup is affected by that issue.
I'm busy with other issues recently, so it's been delayed these days, Sorry. The point is that Nvidia's proprietary driver can not be supported, Because this driver doesn't work with KMS very well and KMS is the prerequisites of Plymouth. Which means if you are using proprietary display driver, you must disable Plymouth at same time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Zhao Qiang 赵强 from comment #8)
I'm busy with other issues recently, so it's been delayed these days, Sorry. The point is that Nvidia's proprietary driver can not be supported, Because this driver doesn't work with KMS very well and KMS is the prerequisites of Plymouth. Which means if you are using proprietary display driver, you must disable Plymouth at same time.
Ok. Let's uninstall plymouth when installing NVIDIA packages for TW/sle15. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c10 --- Comment #10 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Stefan Dirsch from comment #9)
(In reply to Zhao Qiang 赵强 from comment #8)
I'm busy with other issues recently, so it's been delayed these days, Sorry. The point is that Nvidia's proprietary driver can not be supported, Because this driver doesn't work with KMS very well and KMS is the prerequisites of Plymouth. Which means if you are using proprietary display driver, you must disable Plymouth at same time.
Ok. Let's uninstall plymouth when installing NVIDIA packages for TW/sle15.
Not so easy, since plymouth is required by plymouth-dracut apparently. And when obsoleting both by the nVIDIA KMP, the created initrd lacks plymouth so you get a blank screen for a pretty long time or alike. So this doesn't seem such a clever idea. Do we still have a way to specify additional kernel commandline options somewhere, so we can add "plymouth.enable=0" by default when installing nvidia? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c15 --- Comment #15 from Stefan Dirsch <sndirsch@suse.com> --- Seems I've tested something stupid. I've made a clean full-encrypted LVM installation and now the combination omit_dracutmodules+="plymouth" for initrd creation and splash=silent as kernel command line parameter works for me. I've been asked for a password for the encrypted LVM partition setup. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c16 --- Comment #16 from Takashi Iwai <tiwai@suse.com> --- (In reply to Stefan Dirsch from comment #15)
Seems I've tested something stupid. I've made a clean full-encrypted LVM installation and now the combination
omit_dracutmodules+="plymouth"
for initrd creation and
splash=silent
as kernel command line parameter works for me. I've been asked for a password for the encrypted LVM partition setup.
This can be a difference between the encryption of the root fs and of the home directory, too. When a home directory is encrypted while the root fs isn't, the decrpyto password is asked after initrd, thus the system thinks it's done via plymouth. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c18 Andreas Nordal <andreas_nordal_4@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas_nordal_4@hotmail.co | |m --- Comment #18 from Andreas Nordal <andreas_nordal_4@hotmail.com> --- I seem to be getting this symptom both with and without nomodeset. This happened after an update and reboot with TW this morning. Neither the graphical or nongraphical password prompt is showing, working, or giving any visual feedback as I'm typing my password for my /home partition. Instead, I get to see either a HP splash screen or the last log message, and it hangs there. For all I know, it may be related to bug 1205309, which is more recent and ongoing, except I don't have a keyfile in my /etc/crypttab and grub works ��� I can boot in single-user mode, but this may just be because I don't have the problem of decrypting my root filesystem. https://bugzilla.opensuse.org/show_bug.cgi?id=1205309 I'm not using any proprietary drivers. I'm writing this in single-user mode, which allowed me to mount my files, switch user and run startx. Thank goodness this workaround works so well. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 http://bugzilla.opensuse.org/show_bug.cgi?id=1047225#c19 --- Comment #19 from Andreas Nordal <andreas_nordal_4@hotmail.com> --- Uninstalling plymouth solved it for me too, but I'm not using nomodeset. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com