Hide Forgot
+++ This bug was initially created as a clone of Bug #720027 +++ When adding a serial console, the rule has always been that the last console listed on the kernel command line is "primary", so the normal entry is something like "console=tty0 console=ttyS0,115200". Per the comment in /etc/init/serial.conf, a serial console getty will only be started for the last console (if it is serial). However, it appears that upstart sends init messages only to the _first_ console listed, not the last. If you use the above console config, the init messages go to the VGA TTY. If you reverse the console entries, the init messages go to the serial console (but now you don't get a getty for login). One or the other of these two should be changed, and since the historical behavior matches the comment in /etc/init/serial.conf, upstart should be changed. This is also a bug in Fedora 14. --- Additional comment from plautrba on 2011-07-12 07:36:18 EDT --- This is most likely plymouth issue. Does it help if you add rd_NO_PLYMOUTH to kernel command line? --- Additional comment from linux on 2011-07-12 09:05:13 EDT --- You are correct, it does appear to be plymouth related. When I add rd_NO_PLYMOUTH, "console=tty0 console=ttyS0,115200" works as before (kernel messages go both places, init messages to serial, and a getty is started on serial as well).
FYI: I just tried this with F16-Beta and the same problem occurs (sorry I didn't get to checking it in newer Fedora sooner). Adding rd.plymouth=0 fixed it.
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.