That error with mkimage during nand-sata-install is fairly common on XU4 and usually harmless if the system boots fine afterwards. The tool is a bit outdated and often throws this warning even when U-Boot is written correctly. Since it’s working after reboot, I wouldn’t worry about it.

Here is the commit: https://github.com/Guation/radxa-cubie-a5e-armbian-build/commit/202f1bf3943e2a583e10405f54b206fae9991a98

@sivert The "edge" kernel 7.x is more or less the stock kernel from upstream. It's missing some specific K1 drivers developed by SpacemiT basically. I think, upstream devs may implement their own version, thus may need some time. I am not sure, if upstream has the necessary SoC register documentation or if they persue some reverse-engineering on this. I recommend sticking with "current". HTH // Sven-Ola

@0757myt: Thank you so much for your clarification. I am really sorry that some parts of the guide are written too briefly. Sometime I don't know how to explain all of this messy things to new users. @hmoob I looked at your board and it seems your board doesn't have a power IC. There are just some diodes and capacitors near the DC port. May be one of them get shorted or burned but they are not really important. If you are good at soldering, you can definitely find the points for + and - pin to power the board so we will have 1 more USB port. Home Assistant need docker supports. Make sure that you are using the latest image (v1.1): https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/tag/kernel-6.6-armbian-26-v1.1

Since you cannot trust this EMMC, @magixx256 Here is how to get log2ram up and running, plus a quick way to double-check your storage health. 1. Install log2ram Manually Run these commands to pull the official repository, install it, and get it running: # Download and extract the latest release curl -L https://github.com/azlux/log2ram/archive/master.tar.gz | tar zx # Move into the folder and run the installer cd log2ram-master sudo ./install.sh # Clean up the installer files cd .. && rm -rf log2ram-master Reboot to Activate It For log2ram to properly hijack the logging system and mount it into RAM, you need to reboot the machine: sudo reboot Verify It's Working Once the box boots back up, run your status command again: systemctl status log2ram You should see an active (exited) status (which is normal for this service, as it just runs a script at boot to create the RAM disk). You can also verify it's actively mounting by checking your system disks: df -h | grep log2ram You'll see a line showing /var/log mapped to log2ram with a size of about 40MB or 50MB. 2. A Quick Note on System Stability Since log2ram holds your logs in memory and only writes them to your eMMC/SD card once a day (or right before a clean shutdown), a sudden power pull means you lose the logs from that day.