Werner

English caption .srt added (untested) https://fi.mirror.armbian.de/.meeting/

So they indeed did reconsider at this point. Nice.

Are you sure about that? IIRC it was SPI, eMMC and microSD last. See page 30 at https://www.t-firefly.com/download/Firefly-RK3399/docs/TRM/Rockchip RK3399TRM V1.3 Part1.pdf I know this is for RK3399 but I assume Rockchip did not reconsider their boot order in the mean time?

It is probably documented somewhere but wasn't in the mood to do extra research for it. Feel free to DIY.

Not necessarily. It depends on what is on the eMMC. The order you described would work only if there is a boot loader on eMMC that checks for microSD presence and points there if found. If however the boot loader on eMMC is dumb and doesn't care about other bootable devices it just runs through, which can be a big issue if the eMMC module cannot disabled or removed from the board. I faced a similar issue long time ago when I had a pinebook pro in my collection. The fixed boot order of rk3399 is SPI, eMMC, SD. RK3588 might be similar. This default behavior cannot be altered, only worked around by telling the boot loader, that is going to be flashed to SPI or eMMC, to look for microSD first.

Did you take note here?

Tried within armbian-config? If that does not work make yourself familiar with userspace-specific network configuration. Like for example Ubuntu using netplan.

If there is no older version in archive then it is gone.

Please ALWAYS share full logs by uploading them as suggested in the last lines of the output to paste.next.armbian.com. This helps us to understand what happened better.

Went nicely through for me with 1.8/2.4GHz: https://browser.geekbench.com/v5/cpu/21177042 Only difference is a slightly adjusted kernel with debugfs removed and WiFi support removed entirely. Should not have an impact though.

https://fi.mirror.armbian.de/apt/pool/main/l/linux-5.15.92-bcm2711/

I think this pretty much sums it up: https://docs.armbian.com/User-Guide_FAQ/#why-i-cannot-simply-shove-a-random-image-into-my-board-to-work-like-on-my-pc tl;dr: no

Is the firmware file present?

moved since not an actual tutorial but request for assistance. Try something like here: https://github.com/glasgowneuro/comedi_raspberry_pi_bullseye

- Building issues should go here: https://github.com/armbian/build - non-LTS variants are never really supported but added for interested people to play with without need for any kind of support (which there isn't) - Try Lunar instead of Kinetic since it is most recent non-LTS

I think armbian-install received fixes in the mean time. Try an Orange Pi 5 image from here: https://github.com/armbian/community/

moved to aw

moved to unmaintained

Try code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ARTIFACT_IGNORE_CACHE=yes

Hi, can you share code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -u after successful boot? Cheers

Then I suggest to ask at some place that actually deals with android on these devices. We don't.

It is good enough 🌱] Getting ORAS manifest [ ORAS manifest from ghcr.io/armbian/cache-root/arm64-bullseye-gnome:23.05.0-trunk--gnome-aa7a4a172569B9536b3 ] Error: GET "https://ghcr.io/v2/armbian/cache-root/arm64-bullseye-gnome/manifests/23.05.0-trunk--gnome-aa7a4a172569B9536b3": GET "https://ghcr.io/token?scope=repository%3Aarmbian%2Fcache-root%2Farm64-bullseye-gnome%3Apull&service=ghcr.io": response status code 403: denied: requested access to the resource is denied Probably temporary error. Just retry or disable artifact usage

moved to unmaintained Since the Armbian build framework does more or less the same for you I guess you will find the answer in the source code of it: https://github.com/armbian/build