I used it once as test. Good thing is it does verification. Hopefully that will help kill the counterfeit SD-card sales and various rubbish SD-card adapters. Bad thing (for me at least) is that there is some image caching option on by default. Good for saving excessive re-downloads, but I did not look how it works and where it is stored. I use differential backups, also via slow/expensive mobile links potentially, so don't want to wast bandwidth and volume on some cache image or chunk of data. To help people with images on this forum, I did run/boot various images as container, can be done with sudo systemd-nspawn -b -i <imagefile> (if rootfs in image is just 1 partition ) You need some working ARM64 computer of course, but that can be the old/running version of the one you want to upgrade. So I suggest you do that, or maybe the build environment cache cleaning fails (your setup). Also you involve an SD-card already. What if that card internal firmware messes up blocks. If you anyhow build image yourself, maybe use Btrfs as rootfs, also make sure U-Boot has option enabled, than you have much better ways to pin-point where the problem is. But you already did bold text for file dates I see, so I guess some caching issue somewhere.

/dev/mmcblk0p1 is a partition that contains the filesystem, not a drive. The drive is /dev/mmcblk0 and because you did a low-level sector by sector (or block by block) copy with dd, it also just has the exact same partition table (MBR-table or GPT). Now in modern Linux and various pre-installed images there are methods (possible) to expand the partition and the filesystem to occupy the whole remaining space. It is easier with MBR-table. If GPT, there is a backup GPT at the end of the disk, so in your case 64G. On the 128G SD-card the space after 64G is then hidden. I usually manage all this manually before first boot, with gdisk, not fdisk. As it is text based, it also works via remote ssh and serial console cable. I also deliberately added a dummy partition (number 3) to RPi images in the past so that the auto-expander could not claim the whole SD-card. If no GUI, a Linux install fits within a few GB, especially if you use Btrfs as filesystem for root and use on-the-fly compression (mount option compress-force=zstd). Then it is about 1GB needed, not 100x more.

apply this patch for a working wifi: diff --git a/extensions/radxa-aic8800.sh b/extensions/radxa-aic8800.sh index e3e99eaa8..7ab721353 100644 --- a/extensions/radxa-aic8800.sh +++ b/extensions/radxa-aic8800.sh @@ -10,7 +10,7 @@ function extension_finish_config__install_kernel_headers_for_aic8800_dkms() { function post_install_kernel_debs__install_aic8800_dkms_package() { - if linux-version compare "${KERNEL_MAJOR_MINOR}" ge 6.20; then + if linux-version compare "${KERNEL_MAJOR_MINOR}" ge 7.1; then display_alert "Kernel version is too recent" "skipping aic8800 dkms for kernel v${KERNEL_MAJOR_MINOR}" "warn" return 0 fi

I have tested the latest build (26.2.0-trunk.668) and found that USB 3.0 is still not operational. Has anyone been able to get this working?

I've wasted 2 days now, screwing around trying to make netplan work and not getting anywhere. So I've taken a screenshot of what works on my e5p. I will nuke the 25-04 image I have and dl a fresh one but to test that idea, I'll first get the card from the e5p and see if it works in this one. But first I'll dl an image of the e5p card. And I may have a clue dd died w/o an error at 64G of a 128G card. So now that image is being written to another 128G u-card to see if it becomes an e5p when booted and the network works in which case i'll edit the hostname and see if it is amanda when repowered again. It was pings yahoo.com like it has a license. At 192.168.71.122 at which point I edit the netplan to put it back at amanda's address of 192.168.71.2. If that works, and it did, install gfs2 & 57 deps and mdadm & see if the /raid6 appears on a pd reboot. It did as /dev/vg0/myraid so while this has been a looooong slog, it all works even if its not an approved method. That img has quite a pile of gcode as it been a 3d printer for over a year. burned up a hot end and 20+ kg of filament. All that can go. And its gone quite nicely so far, got the /raid6 stuff installed and its been making a new 6.18 initramdisk img for about 20 minutes. Assuming its found the raid6 and has to fsck 11.2 Tb it might take a while. The busy circle is still rotating. But its still rotating with a new msg, something about permissions despite me being root to run synaptic. But that did NOT prevent it from rebooting from a powerdown. Or preventing me from mounting the /raid6 after creating its mount point. And recovering from that raid6, the rsync based backup driver script that fills it. I'm logged into it from here and here is a df report: gene@amanda:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 385288 6424 378864 2% /run /dev/mmcblk0p1 60102260 12713940 46688204 22% / tmpfs 1926424 0 1926424 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 1926424 68 1926356 1% /tmp /dev/zram1 47960 1524 42852 4% /var/log tmpfs 385284 92 385192 1% /run/user/1000 /dev/mapper/vg0-myraid 11272913680 533576604 10739337076 5% /raid6 So it even thinks /dev/mmcblk01 is a 60G drive, apparently because the one I copied was a 64G, not a 128G like its label says. problem solved but I still haven't the foggiest what the real problem was, only that I burned up two weeks of my remaining life at 91 years old already. Now I need the fstab line that automounts it during the bootup.