Bug 543236

Created attachment 375253 [details]
dmesg

Created attachment 375255 [details]
grub menu.lst

Just out of curiosity I tried running:

/bin/plymouth ask-for-password --prompt /dev/sda3 is password protected --command=/sbin/cryptsetup luksOpen -T1 /dev/sda3 luks-cbb32109-3b6d-433b-8da8-0e7b4f9387a7; echo $?

and got 111 as a result. This makes me think that the reason my encrypted root isn't mounted is because the passkey prompt fails to show up. Why that happens, I'm not yet sure.

Based on the /var/log/yum.log that I found using the liveUSB I have plymouth-0.8.0-0.2009.29.09.19.fc12.x86_64 installed on this laptop.

I just ran /sbin/cryptsetup luksOpen -T1 /dev/sda3 luks-cbb32109-3b6d-433b-8da8-0e7b4f9387a7; echo $? and got:

Enter passphrase for /dev/sda3:
padlock: VIA PadLock not detected.
Intel AES-NI instructions are not detected.
Key slot 0 unlocked.
0

and luks-cbb32109-3b6d-433b-8da8-0e7b4f9387a7 appeared in /dev/mapper

leaving the shell (with ctrl-D) caused dracut to continue booting the system

PING

I would like someone to respond to this issue please. I haven't restarted my laptop since reporting this issue for fear of running into it again. I have about 300 updates outstanding because I don't want to change the state of my system too much.

Re-assigning to plymouth because this doesn't seem like a problem with dracut (I can boot by issuing commands manually) and to get some response about the problem.

duplicated output messages 
and 
"plymouthd: ply-keyboard.c:450: ply_keyboard_add_input_handler: Assertion
'keyboard != ((void *)0)' failed."

are two separate issues that were fixed before F12 GA.  Were you running rawhide before upgrading to F12?  If so, you may need to rebuild your initrd with the GA plymouth.

I did not use rawhide. I installed F12 from scratch. How can I rebuild the initrd? When is the initrd rebuilt normally? Does it happen when plymouth is updated? I should try checking if there is a plymouth/dracut update applicable for my system. What should I do in case all of these problems go away after the initrd is rebuilt?

hmm, if this is a fresh install then there must be a lingering issue.

The initrd is rebuilt when doing a new kernel install.

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

I updated my kernel to kernel-2.6.31.9-174.fc12.x86_64.rpm (and kernel-firmware-2.6.31.9-174.fc12.noarch.rpm) and both the main error (no root device) as well as the assertion message are still happening. I made sure that grub is selecting the 2.6.31.9* kernel when booting.

I now have this initrd:
md5sum /boot/initramfs-2.6.31.9-174.fc12.x86_64.img
b52cf2535e0d13b02af11ba792514377  /boot/initramfs-2.6.31.9-174.fc12.x86_64.img

what's the output of

rpm -q plymouth

?

plymouth-0.8.0-0.2009.29.09.19.fc12.x86_64

can you attach your initrd ?

Created attachment 382041 [details]
initrd

thanks.

I've just updated to the following packages and I still get all of the problems mentioned in this bug. I still have to drop into the 'rdshell' in order to enter the luks encryption key and boot my laptop:

Jan 22 17:50:55 Updated: kernel-firmware-2.6.31.12-174.2.3.fc12.noarch
Jan 22 17:51:53 Installed: kernel-2.6.31.12-174.2.3.fc12.x86_64
Jan 23 10:56:40 Updated: libdrm-2.4.17-1.fc12.x86_64
Jan 23 10:56:42 Updated: libdrm-2.4.17-1.fc12.i686
Jan 23 10:56:44 Updated: plymouth-0.8.0-0.2009.29.09.19.1.fc12.x86_64
Jan 23 10:56:44 Updated: plymouth-utils-0.8.0-0.2009.29.09.19.1.fc12.x86_64
Jan 23 10:56:45 Updated: plymouth-gdm-hooks-0.8.0-0.2009.29.09.19.1.fc12.x86_64
Jan 23 10:56:47 Updated: libdrm-devel-2.4.17-1.fc12.x86_64

Created attachment 386346 [details]
newest initrd

ah i missed before that you're doing:

init=/sbin/bootchartd

on your kernel command line.

(In reply to comment #20)
> ah i missed before that you're doing:
> 
> init=/sbin/bootchartd
> 
> on your kernel command line.    

I just tried removing this from the kernel line(s) and all of the sudden I was able to boot properly into my laptop.

I built 0.8.0-0.2009.29.09.19.3 that should help with this. mind trying?

plymouth-0.8.0-0.2009.29.09.19.3.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/plymouth-0.8.0-0.2009.29.09.19.3.fc12

I'll try this tonight. Which packages should I update? All of them?

all the ones you currently have installed anyway.

Also you'll need to run

dracut -f

to rebuild your initrd with the new plymouth

(as a safety measure, you may want to make sure you have multiple kernels installed or back up your existing initrd and make it an alternate entry in grub.conf)

plymouth-0.8.0-0.2009.29.09.19.3.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update plymouth'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1148

As I said on http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1148, installing plymouth-0.8.0-0.2009.29.09.19.3.fc12 from updates-testing didn't fix the problem for me even after I re-generated the initramfs image.

After figuring out the problem with 'dracut -f' I guess that this does 'fix' the bug, but it's not pretty. If I still have init=/sbin/bootchartd then I get a console prompt for the encryption key. I'm just going to remove bootchart from my system for an easy fix.

ah sorry for the misinformation.  You can also run 

/usr/libexec/plymouth/plymouth-update-initrd


plymouth by default won't show a graphical splash if init= is on the cmdline.  this is so plymouth doesn't interfere with emergency shells and the like.

We could probably special case bootchart.

You can force a graphical splash by putting plymouth:force-splash on the kernel command line.

plymouth-0.8.0-0.2009.29.09.19.3.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.