Red Hat Bugzilla – Bug 461641
plymouth isn't always getting updated after yum updates
Last modified: 2008-09-30 16:31:37 EDT
--- Additional comment from firstname.lastname@example.org on 2008-09-09 12:18:21 EDT ---
Looks like the previous version of plymouth was:
Aug 29 07:12:15 Updated: plymouth-0.6.0-0.2008.08.27.2.fc10.x86_64
But I'm not sure that that explains what I saw. Here's a snippet from my yum log this morning. plymouth is updated to the new version:
Sep 09 07:24:35 Updated: libXft-devel-2.1.13-1.fc10.x86_64
Sep 09 07:24:37 Updated: plymouth-libs-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:38 Updated: plymouth-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:39 Updated: plymouth-plugin-spinfinity-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 07:24:39 Updated: plymouth-plugin-label-0.6.0-0.2008.09.05.3.fc10.x86_64
...new kernel is installed and rpm is updated. At this point -314 would hang at boot time.
Sep 09 07:26:00 Installed: kernel-2.6.27-0.314.rc5.git9.fc10.x86_64
Sep 09 07:26:00 Updated: rpm-4.5.90-0.git8461.5.x86_64
...after I read Yanko's comments, I tried removing plymouth (thinking it might be an optional component):
Sep 09 09:59:24 Erased: mkinitrd
Sep 09 09:59:24 Erased: plymouth-plugin-spinfinity
Sep 09 09:59:26 Erased: plymouth
Sep 09 09:59:26 Erased: plymouth-plugin-label
Sep 09 09:59:27 Erased: plymouth-libs
...plymouth is removed. But looks like mkinitrd depends on it, so I reinstalled it:
Sep 09 10:00:16 Installed: mkinitrd-6.0.62-1.fc10.x86_64
Sep 09 10:00:16 Installed: plymouth-libs-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:17 Installed: plymouth-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:18 Installed: plymouth-plugin-spinfinity-0.6.0-0.2008.09.05.3.fc10.x86_64
Sep 09 10:00:19 Installed: plymouth-plugin-label-0.6.0-0.2008.09.05.3.fc10.x86_64
After this, I tried rebuilding the initrd and was able to successfully boot.
It seems like a yum update of the plymouth package wasn't sufficient to fix whatever the problem was, but uninstalling the package(s) completely and then reinstalling was.
out of curiosity do you have a /bin/plymouthd or /bin/plymouth file (you shouldn't)?
No, neither file exists on this machine.
I have both...
rawhat$ ls /bin/plymouthd
rawhat$ ls /bin/plymouth
steved can you remove them and then run
/sbin/mkinitrd -f /boot/$(uname -r).img $(uname -r)
The following steps did indeed allow my machine to boot
with a serial console:
mv /bin/plymouthd /bin/plymouthd.orig
mv /bin/plymouth /bin/plymouth.orig
/sbin/mkinitrd -f /boot/initrd-$(uname -r).img $(uname -r)
So jeremy fixed this today, I think:
- Remove mkinitrd requires to break the dep loop and ensure things
get installed in the right order