Description of problem: When using VGA and also serial console on qemu guest, VGA console does not write anything after grub boot and serial console is redrawing screen. Because there are too many messages on serial console, boot is slower. Sometimes it looks like boot never ends. Messages on serial console are very disturbing and unable to read them normally. Version-Release number of selected component (if applicable): kernel-PAE-2.6.35.6-48.fc14.i686 qemu-kvm-0.13.0-1.fc14.i686 How reproducible: always Steps to Reproduce: 1. add "console=tty0 console=ttyS0" to kernel boot options 2. (re)boot system Actual results: ... Fedora Welcome to Fedora Welcome to Fedora Welcome to Fedora Welcome to Fedora Welcome to Fedora Welcome to Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to Spustenie udev: Fedora Welcome to ... Expected results: Nice boot like before, only one line displayed per Additional info: If I remove console=tty0 (VGA console output) from grub configuration, boot on serial console is good again. If I remove both console redirections, VGA console is OK. Same problem with both parameters in different order. Because I can't boot fedora-13 kernel under Fedora 14 host, I can't test, if it is an kernel issue or qemu issue. I have no other Fedora 14 computer with serial port.
Looks like same problems on F13 host with F14 kernel, so this looks like a kernel bug. Changing component to kernel.
Note that this bug affects physical systems too. I just noticed this on an F14 system (2.6.35.9-64 kernel). I have not tried the workaround (removing the vga console output).
Is it possible, this is an plymouth problem? After update to plymouth-0.8.4-0.20100823.7.fc14, my system boots better, but there is no boot output on VGA console (tty0). After removal of "quiet" from boot options, kernel output is sent to both serial and VGA console, but system boot don't.
It almost certainly is a plymouth problem.
Changing component to plymouth.
This is a problem for me in F14 also. Anything I can do to help troubleshoot? For now, I've had to remove the 'console=tty0' from grub, which solves the problem.
Same problem on Fedora 16 with GRUB2. Curious, that if I set: GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX nomodeset console=tty0 console=ttyS0" there is no "getty" serial console in fedora. Here are my tested console output orders: grub - grub1|grub2 output, does not matter by parameters, configured in grub.cfg kernel - kernel messages, if there is no "quiet rhgb" boot option services - service boot messages (those which displays [OK], ...) getty - getty login prompt S0 only: grub: both, kernel: serial, services: serial, getty: both 0,S0: grub: both, kernel: both, services: vga, getty: both S0,0: grub: both, kernel: both, services: both, getty: vga required: grub: both, kernel: both, services; both, getty: both May be there need to be fixed only getty loading, when I set ttyS0, tty0 console order. Should this bug be reported against systemd?
See bz#755003 for more suggestions, unfortunately no fully functional solution yet. :-( With rd_NO_PLYMOUTH: 0,S0: grub: both, kernel: both, services: vga, getty: both S0,0: grub: both, kernel: both, services: serial, getty: vga with: ln -s /lib/systemd/system/serial-getty@.service /etc/systemd/system \ /getty.target.wants/serial-getty 0,S0: grub: both, kernel: both, services: both, getty: both S0,0: grub: both, kernel: both, services: both, getty: brokenserial Can plymouth release serial console before agetty processes are started?
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.