tgillett

@well83 Thank you for that u-boot file - the device now boots up into the Armbian login page. Once I replaced the login credentials, the system runs as expected. Many thanks for your help. It does beg the question though, where did this particular uboot file come from, and more generally what is the process for producing u-boot files? Once again, many thanks for your help.

@well83 The device I have is labelled A95X-F3-Air and it operates happily on the earlier Armbian firmware using uboot-s905x2-s922 file and /dtb/amlogic/meson-sm1-a95xf3-air.dtb Link: https://drive.google.com/open?id=1n6CZa582uJECV3lzQDtFbmbyvmOSiUSg Filename: Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz So I am reasonably confident that all the components are ok. I went through the process as you outlined for installing 6.1.11: 1. Downloaded version 6.1.11 from here: https://mirror-us-phx1.armbian.airframes.io/dl/aml-s9xx-box/archive/ ( filename is Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11_xfce_desktop.img.xz), and checked the sha256sum out all ok. 2. Edit the /extlinux/extlinux.conf file as follows: LABEL Armbian LINUX /uImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb #FDT /dtb/amlogic/meson-sm1-a95xf3-air-gbit.dtb FDT /dtb/amlogic/meson-sm1-a95xf3-air.dtb append root=UUID=505123a0-7aa3-403f-b86b-27e32bc39aef rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles 3. I then copied the uboot file uboot-s905x2-s922 to u-boot.ext 4. Safely removed the SD card and installed on the A95X device. 5. Powerup sends a screen signal to the monitor as shown by the calibration LED, but otherwise a blank screen. I feel I am missing some basic step, but I can't see what it it. Any suggestion s appreciated.