Hi,
I am looking into optimising/fixing console parameters for
RPi images generated by [1]. The thing is that these images
have console=ttyS0 hardcoded which is not valid for RPi’s
which do not have bluetooth module or RPi 5 devices. I have
few RPi machines which should use following console:
ttyAMA0 - Raspberry Pi 2 Model B Rev 1.2
ttyS0 - Raspberry Pi 3 Model B Plus Rev 1.3
ttyS0 - Raspberry Pi 4 Model B Rev 1.1
ttyAMA0 - Raspberry Pi Compute Module 3 Rev 1.0
ttyS0 - Raspberry Pi Compute Module 4 Rev 1.0
ttyAMA10 - Raspberry Pi 5 Model B Rev 1.0 (c0 stepping)
ttyAMA10 - Raspberry Pi Compute Module 5 Rev 1.0 (dO stepping)
Currently raspberrypi-firmware-dt package which provides device
tree files for these boards define proper chosen { stdout-path = }.
Which means that if there is no console= parameters on the kernel
command line the one defined in stdout-path will be used for
kernel logging. And this is working fine. I have tested this on
the above boards.
So far so good.
Now ... images witch boot to graphical desktop have also cconsole=tty0
which presumably redirect kernel boot log to graphical console.
If I remove all console= parameters from these images the boot log is
redirected to serial output and once graphical login is stared it will
be visible on the HDMI output.
One thing I am unsure is: if I don’t add serial console to the kernel
command line will system spawn agetty for preferred kernel console?
Question is can we remove serial console= from the command line, can we
remove tty0 (graphical console) also?
Regards,
Ivan
[1] https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS
