Sorry for taking so long to try this, I decided to solder thicker and shorter wires onto the board to make sure that isn't the issue. Unfortunately it still crashes after a short while but nothing is seen in ssh session: ~# tail -f /var/log/Xorg.0.log [ 34.652] (II) event1 - sunxi-ir: device is a keyboard [ 34.722] (**) sunxi-ir: Applying InputClass "libinput keyboard catchall" [ 34.722] (II) Using input driver 'libinput' for 'sunxi-ir' [ 34.722] (**) sunxi-ir: always reports core events [ 34.722] (**) Option "Device" "/dev/input/event1" [ 34.722] (II) libinput: sunxi-ir: is a virtual subdevice [ 34.722] (**) Option "config_info" "udev:/sys/devices/platform/soc/7040000.ir/rc/rc0/input1/event1" [ 34.722] (II) XINPUT: Adding extended input device "sunxi-ir" (type: KEYBOARD, id 😎 [ 34.722] (**) Option "xkb_model" "pc105" [ 34.722] (**) Option "xkb_layout" "us" I am going to mess with the SPI frequency and see if that makes any difference. ----- edit ----- I actually found out that the desktop only freezes whenever I stop using the mouse for 5 seconds.

BOOTFS_TYPE=fat is part of the aml-s9xx-box.tvb config file and has always been. So I'm not sure what your comment is referring to, but it seems to be off topic for this thread which is about instructions for using the aml-s9xx-box Armbian builds.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.14-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.14) + WineD3D / Zink (OpenGL) ~30fps@720p (this game is capped at 30fps) NARUTO SHIPPUDEN - Ultimate Ninja STORM 3 Full Burst HD

@Trinom I know this post is really old but I have to chime in on this. The instructions that @Igor gave you says to use Armbian to boot the device with then use the commands given to install Armbian. Raspbian is not Armbian. Just sayin' Just trying to figure out what or where you were reading.

With the following options configured as a built-in module, the issue does not happen anymore on a poweron. CONFIG_TYPEC=y CONFIG_TYPEC_TCPM=y CONFIG_TYPEC_TCPCI=y CONFIG_TYPEC_FUSB302=y CONFIG_PHY_ROCKCHIP_USBDP=y I can create a pull request for the linux-rockchip64-edge.config file. But not sure what the general consensus on the kernel options for Armbian kernels is. Maybe it is also fixable via some code change, but that would be something for a real kernel developer.