Serial Console Configuration Question

[mlitke]

Anyone know why the service for the serial console on the Raspberry Pi is set up as a regular getty and not a serial getty?

In the Raspberry Pi image, there is a symlink, /etc/systemd/system/getty.target.wants/ ... A0.service, that links to /usr/lib/systemd/system/getty@.service (instead of linking to, /usr/lib/systemd/system/serial-getty@.service). Linking to the regular getty file instead of the serial getty file causes the baud rate to change once the boot process reaches the login service. The baud rate for the boot messages (set by the kernel option: console=ttyAMA0,115200) is 115200, but the baud rate set in the regular getty configuration is 38400, so the baud rate for the boot messages is 115200, but the getty baud rate (which is used once the login service starts) is 38400. If the serial console symlink linked to the serial getty, the baud rate can be 115200, 38400, or 9600.

Prior to implementing systemd, the install images had the serial console baud rate set to 115200 (here is the line from /etc/inittab: c2:2345:respawn:/sbin/agetty -8 -s 115200 ttyAMA0).

[pepedog]

You are right, I missed that. All we need is a way to remind me next time. I will forget.
Tell me also exactly what to change too, please.

[mlitke]

I am not sure what I can do to help remind you, any ideas? Is there a bug tracking/change request system you all use to track issues/requests?

To make the change, remove the current symlink:
$this->bbcode_second_pass_code('', 'prompt> rm /etc/systemd/system/getty.target.wants/getty@ttyAMA0.service')

And then add a new symlink that points to the serial getty:
$this->bbcode_second_pass_code('', 'prompt> ln -s /usr/lib/systemd/system/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty@ttyAMA0.service')

That should be it.

[pepedog]

My system is a piece of paper on my desk. I already had a note to do this, found paper only today. Sorry, will be done.

[mlitke]

Cool, thanks.