The arm64 minimal install ISO does not properly set the baud rate when starting the getty for the serial port specified in the console kernel command line parameter. Reproducible: Always Steps to Reproduce: 1. Boot the arm64 minimal install ISO on a Radxa ROCK 5B+ 2. Append 'console=ttyS2,1500000' to the 'Boot LiveCD (kernel: gentoo)' boot entry (after cdroot) and hit F10 Actual Results: The serial console output stops after: * Adjusting inittab ... * Adding ttyS2 console to inittab ... [ ok ] [ ok ] * Starting local ... [ ok ] Expected Results: The serial console output should show: * Adjusting inittab ... * Adding ttyS2 console to inittab ... [ ok ] [ ok ] * Starting local ... [ ok ] livecd login: root (automatic login) Welcome to the Gentoo Linux Minimal Installation CD! The root password on this system has been auto-scrambled for security. If any ethernet adapters were detected at boot, they should be auto-configured if DHCP is available on your network. Type "net-setup eth0" to specify eth0 IP address settings by hand. Check /etc/kernels/kernel-config-* for kernel configuration(s). The latest version of the Handbook is always available from the Gentoo web site by typing "links https://wiki.gentoo.org/wiki/Handbook". To start an ssh server on this system, type "/etc/init.d/sshd start". If you need to log in remotely as root, type "passwd root" to reset root's password to a known value. Please report any bugs you find to https://bugs.gentoo.org. Be sure to include detailed information about how to reproduce the bug you are reporting. Thank you for using Gentoo Linux! root@livecd ~ # When changing the baud rate of the serial console to 115200 in U-Boot, then adding console=ttyS2,115200 to the kernel command line, I get the expected result.
Looking at /etc/init.d/fixinittab, it has this: # EFI-based machines should automatically hook up their console lines if dmesg | grep -q '^Adding console on' ... Running a slightly modified version of that command manually doesn't return anything: root@livecd ~ # dmesg | grep ^Adding root@livecd ~ # The system is definitely booted via EFI: root@livecd ~ # ls /sys/firmware/efi/efivars/ AuditMode-8be4df61-93ca-11d2-aa0d-00e098032b8c Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c DeployedMode-8be4df61-93ca-11d2-aa0d-00e098032b8c OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c RTStorageVolatile-b2ac5fc9-92b7-4acd-aeac-11e818c3130c SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c VarToFile-b2ac5fc9-92b7-4acd-aeac-11e818c3130c VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c
Looking at https://gitweb.gentoo.org/proj/livecd-tools.git/tree/livecd-functions.sh it appears the highest supported baud rate is 115200, which could explain why I'm experiencing this problem.
