Igor

Which desktop environment?

Aha, ok, we merge this then. Remaining ones for H616 some other day ...

Switch to v22.11 or to master and it will work.

This is in the boot logs: ERROR: Did not find a cmdline Flattened Device Tree Nanopi Duo never reached mainline. It only lives in Armbian and it seems this problem is because our complete patch-set was not adopted to 6.x yet. @going is still working on it and dunno how much work there is behind. It will work if you build a CURRENT image.

Check pinned topic in this forum.

Can you try with images from 1st of December?

In a couple of days once repository is updated and synced across download network. Or switching to beta repository ... which is good for testing not recommended for production. Kernel recompilation per release is not yet in function. I only tested it, but we don't have enough build hardware for native compilation.

Yes, exactly.

Those problems you need to resolve with Radxa. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity Armbian download pages: https://www.armbian.com/download/

Made a release build & images are uploading and syncing. This will take at least a day ... we continue to test. Repository update can wait a bit.

Thank you. I have sent you email.

Check if something important is missing from the docs - if you have added pull requests to the Github without a Jira ticket, then its missing from the list. Please add now!

Latest images are broken due to changes in upstream tool flash-tool (damn Ubuntu) ... previous images from archive or rolling must work. We are working on a new release where this will be fixed. (upcoming weekend). Since release activities are anyway unpaid full time job for several people, this can't be fixed in by the way fashion.

fixed with https://github.com/armbian/build/commit/e8f441a7e38a8ecd931c47f27e25890711f64d61

This seems to fix it.

Docker works on official builds: _____ _ _ _ _ |_ _(_)_ __ | | _____ _ __| |__ ___ __ _ _ __ __| | | | | | '_ \| |/ / _ \ '__| '_ \ / _ \ / _` | '__/ _` | | | | | | | | < __/ | | |_) | (_) | (_| | | | (_| | |_| |_|_| |_|_|\_\___|_| |_.__/ \___/ \__,_|_| \__,_| Welcome to Armbian 22.11.0-trunk.0121 Jammy with Linux 5.15.80-rockchip No end-user support: untested automated build System load: 5% Up time: 5 min Memory usage: 6% of 1.96G IP: 172.17.0.1 10.0.30.119 CPU temp: 48°C Usage of /: 85% of 15G RX today: 85.4 MiB [ 0 security updates available, 2 updates total: apt upgrade ] Last check: 2022-11-28 00:55 [ General system configuration (beta): armbian-config ] Last login: Mon Nov 28 00:47:24 2022 from 10.0.10.12 tinkerboard:~:# sudo docker run -d --name hello hello-world 52aa4db25eb9c143570665ba5f3f38f9c3d9e1fc7ae8757b7664c6a9c9d4b76d tinkerboard:~:# docker run hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (arm32v7) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ tinkerboard:~:# https://github.com/armbian/build/pull/3830 If you run old images, or some in between, it might fail.

Damn Rockchip. I have no issues (except PCI timeouts) with this: Armbian_22.11.1_Rockpi-4b_jammy_current_5.15.79_gnome_desktop.img.xz https://paste.armbian.com/sahalaxuru

New RC images are out. 22.11.1

I think i know how to fix that ...

Impossible. Perhaps you stumbled to archive mirrors which contains all old images? Here you can observe which mirrors we have and how they are organised: https://github.com/armbian/mirror No, because this is best mirror for your location.

Can you try to use recommended flashing tools? I never tried Rufus ... try decompressing image before using it with Rufus. That might be a problem?

No, problem is identified, but we don't have resources / money to proceed from here. For us, this is 24/7, for you - when something breaks down.

We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford.

You are not running kernel provided by Armbian. Perhaps that is the reason?

It is difficult to say what is wrong, but if you are using Armbian you should follow Armbian documentation, not something in between. It can be very different. Vendors are usually using binary boot loaders and proprietary tools they got from chip vendor, while we use open source tools we and community developed. After you erase or disable (connecting pin 23 and 25) SPI, you don't need to do anything else then booting from SD card and using standard armbian-install utility to flash to eMMC boot/eMMC root or eMMC boot/NVME root. We invested a lot of efforts to keep the same install procedure on very different methods ... If there are any hacks needed, they are exposed at download pages https://www.armbian.com/rockpi4/ If you have eMMC to SD card adaptor, that you flash directly and it should work. But like I said, without logs we are in the dark ...