Red Hat Bugzilla – Bug 466247
Information about boot process ends only in /var/log/boot.log, not on screen
Last modified: 2013-04-30 19:41:17 EDT
Description of problem:
When I'm booting machine last message shown in virtual console is that SELinux policy is loaded. After that (new root & plymouth is started) all information ends in /var/log/boot.log but it is not duplicated to virtual console.
When I create initrd without plymouth stuff boot process is written to console as expected.
Version-Release number of selected component (if applicable):
# rpm -qa |grep plymouth
Steps to Reproduce:
1. boot kernel with initrd with plymouth stuff
no messages printed to console after plymouth is started, messages ends in /var/log/boot.log only
messages in /var/log/boot.log and on console as well
I'm able to reproduce this problem only on ppc (I don't test it on other archs) when I access it through KVM switch. Text boot works as expected on my x86_64 laptop/workstation. Let me know if you need access to test hardware.
what's the output of
Well, with latest plymouth (0.6.0-0.2008.10.08.1.fc10) I'm able to boot with "console=hvc0" so output is:
# cat /proc/cmdline
ro console=hvc0 ro root=UUID=bd292de0-344c-44ab-9c98-069967e63079
Oh, so is the issue that messages are going to the serial console and not to the virtual console?
if so, does booting with
fix your issue?
This bug has been triaged
I did next inspection about this issue and it seems problem is not in plymouth. /dev/hvc0 doesn't exist when plymouth starts and due this no output is written to KVM console. When I add "mknod /dev/hvc0 c 229 0" command to initrd's init script all works fine.
As is written in comment #5 reassinging to mkinitrd. Initrd should create /dev/hvc0 on systems where that console exists. (For example something like [ -e /dev/hvc0 ] && emit "mknod /dev/hvc0 c 229 0")
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Fixed in git
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.