Created attachment 247841 [details] var/log/messages from boot -v FreeBSD14-stable orange pi 5 plus I see the same problem in FreeBSD 13.2 serial console works during the efi boot steps. The console looks like this: Setting currdev to disk0p2: Loading /boot/defaults/loader.conf Loading /boot/defaults/loader.conf Loading /boot/device.hints Loading /boot/loader.conf The processors are identified and then serial output stops. Final output looks like this: output to serial always stops here--> I/TC: Secondary CPU 7 switching to normal world boot. --- # dmesg | grep uart uart0: <16750 or compatible> iomem 0xfeb50000-0xfeb50fff irq 21 on acpi0 uart0: fast interrupt uart0: PPS capture mode: DCD -- never see that typical line--> uart0: console (115200,n,8,1) I filed a bug report with the github efi project. https://github.com/edk2-porting/edk2-rk3588/issues/118 --- I made the change as suggested to: sys/dev/uart/uart_dev_ns8250.c line 452 {"HISI0031", &uart_ns8250_class, 0, 2, 0, 24000000, UART_F_BUSY_DETECT, "HiSilicon / Synopsys Designware UART"}, ----- I see the same problem with serial port. Need guidance on how to fix this problem
Is there an ACPI method or property to get the base clock ? Patching like you did will break what ever other hardware this compat was added for.
Created attachment 247847 [details] output --> sysctl -ad attached a sysctl list from a non-patched system
sysctls won't help, do : pkg install acpica-tools /usr/local/bin/acpidump -b and post the .dat file here.
Created attachment 247848 [details] acpidump -b
Created attachment 247879 [details] ns8250: Try to get the clock-frequency property Please try with this patch.
Created attachment 247889 [details] acpidump after patch
the same results, no terminal. attached new acpidump
No need to upload acpidump each time, this won't modify the table. Also it looks like that my patch is useless because we already try to get the clock-frequency property (https://cgit.freebsd.org/src/tree/sys/dev/uart/uart_bus_acpi.c#n99) so I don't really know why it doesn't work here. Can you share a boot -v, it might contain more info
Created attachment 247917 [details] boot -v terminal output and var-log-messages