pierre-pret

I found the same restart problem. If I take the latest official Orange PI debian bullseye image and copy /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb and the /boot/dtb/allwinner/overlay/*h6* files to the Armbian debian bullseye image (5.1 kernel downloadable under archive, not latest) then the reboot problem is resolved.

With Armbian 22 (kernel 5.15 and bullseye/jammy) the Orange PI 3 LTS worked great including WiFi, ETH, Bluetooth. Partly thanks to @Ukhellfire and @going. Downloadable here: https://xogium.performanceservers.nl/archive/orangepi3-lts/archive/ Below is what I find the status is for the new Armbian 23 images provided for here : https://www.armbian.com/orangepi3-lts/ Branch current: Main downloads Armbian 23 with kernel 6.1 bookworm: It boots, but every 3rd or 4th keystroke is ignored. No ETH, no WiFi. Armbian 23 with kernel 6.1 jammy: It boots, keystrokes are OK, ETH is OK, but WiFi doesn't work. Branch edge: Rolling release downloads Armbian 23 with kernel 6.4 bookworm: Doesn't boot, no board lights come on. Armbian 23 with kernel 6.4 lunar: Doesn't boot, no board lights come on. Branch edge: When I build myself There doesn't seem to be any selection to make edge boot regardless of kernel (5.15, 6.1 or 6.4) or bookworm/bullseye. Branch current: When I build myself I found a way to get a good build of Armbian 23: use branch current with legacy kernel 5.15: 1) Checkout the last current commit: https://github.com/armbian/build/commit/6af50cfcdd46661038fd30c71548362012df6438 2) Edit config/boards/orangepi3-lts.csc and add support for legacy kernel: KERNEL_TARGET="legacy,current,edge" 3) Build legacy bullseye: ./compile.sh build BOARD=orangepi3-lts BRANCH=legacy RELEASE=bullseye @Igor I can send free Orange PI 3 LTS boards to US based Armbian contributors if it can improve community support of this board.

We flash hundreds of Orange PI 3 LTS boards with stock Armbian Debian Bullseye via nand-sata-install to install it on the onboard eMMC storage. Some boards after running for a week or more would randomly give this error and fail to boot: Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay* (did the system wait long enough?) - Missing modules (cat /proc/modules: ls /dev) ALERT! /dev/mmcblk0p1 does not exist (initramfs) We can turn the board on and off as many times as we want, the error persists. We can fix the problem by booting it from an Armbian SD again, mount the eMMC drive, then shut it down. We don't change any files. For some reason only mounting it from eMMC make it boot fine again. This has been confirmed with many boards. Any idea what can be going wrong or what we can manually add to the image to prevent it?

Please make a pull request. I just made my first pull request to fix Bluetooth here: https://github.com/armbian/build/pull/3896