Can’t get the pi-gadget I built to load. Reverted basically to the same uc20 branch from github and built it and surprisingly it did not work again.
I unsquashfsed my snap and the one from the upstream and ran a diff on it. This is the result:
diff -r squashfs-root-canonical squashfs-root Binary files squashfs-root-canonical/boot-assets/boot.scr and squashfs-root/boot-assets/boot.scr differ diff --color -r squashfs-root-canonical/boot-assets/config.txt squashfs-root/boot-assets/config.txt 4c4 < dtoverlay=vc4-fkms-v3d,cma-128 --- > dtoverlay=vc4-fkms-v3d,cma-256 33c33 < disable_splash=1 \ No newline at end of file --- > disable_splash=1 Binary files squashfs-root-canonical/boot-assets/psplash.img and squashfs-root/boot-assets/psplash.img differ Binary files squashfs-root-canonical/boot-assets/uboot_rpi_2.bin and squashfs-root/boot-assets/uboot_rpi_2.bin differ Binary files squashfs-root-canonical/boot-assets/uboot_rpi_3_32b.bin and squashfs-root/boot-assets/uboot_rpi_3_32b.bin differ Binary files squashfs-root-canonical/boot-assets/uboot_rpi_4_32b.bin and squashfs-root/boot-assets/uboot_rpi_4_32b.bin differ Only in squashfs-root-canonical/snap: manifest.yaml Only in squashfs-root-canonical/snap: snapcraft.yaml
The one from upstream has this file uboot_rpi_4_32b.bin dated 12 November with the binary size of 537072.
The one I have in my snap seems to be from February 11, 2020. And I thought maybe they are the reason. But after replacing them in my snap it still did not boot.
The other different file was boot.scr. I tried replacing it then in my snap with the one from upstream.
And it actually booted.
This is the diff output: https://hastebin.com/duzugisozu.bash
Another issue that is as severe - there is no splash screen (though maybe that’s because I copied boot.scr from the upstream pi-gadget and it has that disabled somewhere there Idk because it did not show ubuntu splash with the upstream gadget as well).
Any ideas what’s causing this? (building inside armhf ubuntu 20 docker image if that’s of any importance).