Bug 530991 - No password prompt for encrypted root partition with 'nomodeset' parameter
Summary: No password prompt for encrypted root partition with 'nomodeset' parameter
Keywords:
Status: CLOSED DUPLICATE of bug 530896
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-26 12:55 UTC by Andriy Tsykholyas
Modified: 2009-11-15 11:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-15 11:39:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
grub.conf (1.07 KB, application/octet-stream)
2009-10-26 12:58 UTC, Andriy Tsykholyas
no flags Details

Description Andriy Tsykholyas 2009-10-26 12:55:00 UTC
Description of problem:
If Fedora 12 (F12) Beta is booted with 'nomodeset' kernel parameter there is no prompt for root partition password, just black screen.
After typing the password the boot process resumes and finishes successfully.

Version-Release number of selected component (if applicable):


How reproducible:
Always.

Steps to Reproduce:
1. Install F12 beta with root partition encrypted.
2. Add new grub entry (or modify existing one) with 'nomodeset' parameter.
3. Boot F12.
4. Wait a bit.
  
Actual results:
At first a colored line starts to move at the bottom of the screen (same as on Fedora 10 boot). Than screen becomes black. 

Expected results:
Boot screen should be similar with one without 'nomodeset' parameter (Fedora symbol in the center of the screen changing its color) followed by a password prompt for a root partition. 

Additional info:
The machine is MSI Wind U100 with Intel GMA 950. 
The reason why I use 'nomodeset' is that otherwise there is a huge screen flickering on user login and it is almost impossible to login. And 'Common F12 bugs' suggest using 'nomodeset': https://fedoraproject.org/wiki/Common_F12_bugs#intel-misc-gfx

F12 Beta was installed using the Grub of another Linux on same machine. Installation was done from Beta ISO image (Fedora-12-Beta-i386-DVD.iso) located on the USB stick. The installation process was flawless.
F12 partition schema:
/boot is on sda5, size - 250Mb;
/ is on encrypted logical volume, size - 5Gb.

Comment 1 Andriy Tsykholyas 2009-10-26 12:58:45 UTC
Created attachment 366098 [details]
grub.conf

Attaching my grub.conf.
First entry is original, second - added by me. The only difference is 'nomodeset' kernel parameter.

Comment 2 Milan Broz 2009-10-26 13:23:57 UTC
The password prompt is processed by plymouth, fixing component.

Comment 3 Andriy Tsykholyas 2009-10-29 12:56:29 UTC
Reinstalled same F12 beta on the same machine using external HDD instead of USB stick to store ISO image.
Problem still present.

Comment 4 Andriy Tsykholyas 2009-11-13 06:34:41 UTC
I've updated my system (there were some plymouth* packages updated). Now instead of a completely blank screen there is a blank screen with following password prompt:
"/dev/dm-6 is password protected:"
After filling the password in the boot proces continues normally.

Here are packages that may be related:
plymouth-utils-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-scripts-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-gdm-hooks-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-libs-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-plugin-two-step-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-theme-charge-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-system-theme-0.8.0-0.2009.29.09.19.fc12.i686
plymouth-plugin-label-0.8.0-0.2009.29.09.19.fc12.i686

Due to there is a visible password prompt now, I think this bug can be closed.
Thanks.

Comment 5 Bradley 2009-11-15 11:39:15 UTC
Dupe of bug 530896. See https://fedoraproject.org/wiki/Common_F12_bugs#encrypted-password-for-text-boot

*** This bug has been marked as a duplicate of bug 530896 ***


Note You need to log in before you can comment on or make changes to this bug.