Description of problem:
When starting system with this order of consoles:
I plan to use both VGA and serial consoles on my system. Problems running other combination of console settings is described in bug#652215 (which started with Fedora 14).
But if console=ttyS0 is not default console (last kernel parameter), systemd doesn't start getty service on this console. Please update autodetection or make at least some workaround to overwrite this setting.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot kernel with: nomodeset console=ttyS0 console=tty0
no getty on serial console
login: prompt on serial console
A workaround is:
ln -s /lib/systemd/systemd/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty@ttyS0.service
(In reply to comment #1)
> A workaround is:
> ln -s /lib/systemd/systemd/serial-getty@.service
Doesn't work. Even if "login:" prompt is displayed, I can't type my login/password. When typing "root" it presses enters and ends with "Login incorrect". :-(
Fedora release 16 (Verne)
Kernel 3.1.1-1.fc16.x86_64 on an x86_64 (ttyS0)
fedora-16 login: root
First time login is accepted, but password is entered after first char is pressed. Looks like agetty process works well, but when login is started, it is sharing /dev/ttyS0 with another process. lsof doesn't say anything interesant for me.
That's likely not a systemd bug, but plymouth doing funky stuff with the terminal settings. See https://bugzilla.redhat.com/show_bug.cgi?id=691374#c4 for a workaround.
(In reply to comment #0)
> But if console=ttyS0 is not default console (last kernel parameter), systemd
> doesn't start getty service on this console. Please update autodetection or
> make at least some workaround to overwrite this setting.
So this is expected behaviour. Only the last console= gets a serial getty spawned automatically by systemd.
That leaves us with the issue of broken serial console settings, which is a plymouth bug.
*** This bug has been marked as a duplicate of bug 691374 ***