Ferdinand

Wouldn't it be good to mention this bug/ issue on: Freescale i.MX6 - Armbian Documentation And maybe link to a write-up on how to boot using distro boot? How can I help with testing & analyzing this issue further?

As I can only post one message a day and it's also not possible to edit one of my earlier posts, I choose to follow up here as this is the topic were I initially posted the issue with my cubox-i. I followed the workaround/switch to distro boot/ extlinux boot option as described in: Cubox I1-300-D: initial Armbian flash screen, then "no signal" Initially with the exact same image, the standard Armbian Ubuntu image Armbian_20.02.7_Cubox-i_bionic_current_5.4.28_desktop.7z, then: - Created the extlinux directory in the boot directory of the SD-card; - Added the extlinux.conf file from the topic This worked. Then I took the latest Armbian Bullseye image and took the same approach though with a changed PARTUUID as root partition identifier. This also worked. Latstly, I upgraded to the latest version: So now I am a happy camper! I think a write-up on the cubox-i documentation page can be helpfull for others. As said, I would like to help solve the software rootcause of this issue. Which probably is: Broken ethernet on SolidRun cubox-i (infradead.org) I am not sure how to test and thus help. Please let me know what I can do!

As I seem to have the same issue with my cubox-i, I would like to try this image too. As it's no longer available at the linked location, can you make it available to me somehow? I would like to spend some cycles to find out more about this issue...

Just tried to load Armbian Buster on a Cubox-i. Couldn't see it in the network, so tried HDMI. I saw an Armbian logo and a line: uboot 2018-1... Booting the Solid-Run Debian image, works fine. What should I do to get Armbian working?