Today I upgraded my Helios64, and after reboot it didn't come back. (Waited for 5 minutes or so) After connecting a serial cable (via the USB-C connector), and rebooting, I saw a normal bootloader log (as far as I can see), but no kernel log, just a repeated 'ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)'. I rebooted again, to create a bootlog file, and I saw the same. Then suddenly, after a minute or so, I saw network activity, and my Helios64 was back. Now I have 3 questions. 1) Why didn't it boot twice, and then succeeded? 2) Why is there no kernel bootlog? 3) What is an unhandled SMC? The log ended with ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003) ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003) p104^Gp104^G Armbian 26.5.1 trixie ttyS2 helios64 login: So apparently the serial port is ttyS2. dmesg gave me this info: sudo dmesg | grep tty [ 0.000000] Kernel command line: root=UUID=d03fc106-73e9-4465-89a6-b23dbd26eddd rootwait rootfstype=btrfs splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory [ 0.001587] printk: legacy console [tty1] enabled [ 1.986600] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 31, base_baud = 1500000) is a 16550A [ 1.988766] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 32, base_baud = 1500000) is a 16550A [ 1.988911] printk: legacy console [ttyS2] enabled [ 7.930510] systemd[1]: Created slice system-getty.slice - Slice /system/getty. [ 7.934926] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. [ 7.938724] systemd[1]: Expecting device dev-ttyS2.device - /dev/ttyS2... [ 8.771412] systemd[1]: Found device dev-ttyS2.device - /dev/ttyS2. Is it normal that there are 2 legacy consoles enabled? minicom.cap

In addition, there's a develop branch for the VK_EXT_transform_feedback extension. It is another important requirement for DXVK.

I see no clear error, only something with hdmi-audio-codec, but that is somehow expected AFAIK with mainline based rockchip64 kernel. I think Xfce is X11 and others default to wayland. You can try KDE in X11. 4K is not fully mainlined AFAIK, but you need to check yourself. You can try an edge kernel, is 7.1.x based, maybe it fixes things. I have seen many such issues (RK3588 SoC) in the past, but thing are remarkably fine with 'latest Linux' (KDE6 1080p60, don't have a 4K monitor/TV).

I see several time the following log line: rk-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x2 I do not know what it means, but the fact that is is listed quite often is a hint I would say. There is also an earlier failure w.r.t. PCIE Usually is it power of some incompatibility of the NVME SSD in conjunction with the RK3588 based board. OrangePi5 Pro has questionable device-tree support, that is what I remember. It might be better nowadays, but I guess you will need to try an see if you can get any OS working/recognizing the SSD.

Moved to off-topic.