Red Hat Bugzilla – Bug 458278
Plymouth should not fail on headless systems (serial console)
Last modified: 2013-09-02 02:25:41 EDT
Description of problem:
When installing F10-Alpha with an encrypted root device onto a IBM Power5 ppc system that does not have a vga adapter, the system appears to hang during boot up and not prompt for the passphrase. There isn't anything obvious from the boot.log
During boot-up, plymouth and plymouthd appear to fail when run inside the initrd (encrypted root fs).
I have unpacked the initrd while in rescue-mode on the system, and run the /init script plymouth and plymouthd commands by hand.
Version-Release number of selected component (if applicable):
F10-Alpha, and the following updates:
Steps to reproduce:
$ mkdir /tmp/initrd ; cd /tmp/initrd
$ zcat /boot/initrd... | cpio -id
<ctrl-z> and bg to background the process
$ ./bin/plymouth --show-splash
error: unexpectedly disconnected from boot status daemon
I have posted an strace from both:
* the plymouthd cmd - http://jlaska.fedorapeople.org/plymouthd.strace
* the plymouth cmd - http://jlaska.fedorapeople.org/plymouth.strace
* anytime I install with an encrypted root on a headless ppc system
* system hangs during boot ... does not mount or prompt for encrypted root device
* Normal boot
So the important bit here:
26657 ioctl(10, GIO_CMAP, 0x1001a7d8) = -1 EINVAL (Invalid argument)
26657 ioctl(10, PIO_CMAP, 0x1001a7d8) = -1 EINVAL (Invalid argument)
We can't assume there's a terminal color map to twiddle, and fail fatally if there isn't.
We should also probably go straight to details view in that case, since serial console users probably always want the detailed boot information.
This should work pretty well now. (I'll need to do some more testing before release though)