All Activity

@robertoj Hi I'm completely stuck. I'm trying to build an Armbian Trixie image, but I'm having trouble installing packages. I've tried changing the repository links to the ones closest to my location, but to no avail. I am completely unable to continue my research for assembling Armbian. This is how I collected Armbian ./compile.sh BOARD=orangepizero3 BRANCH=edge kernel-config CONFIG_DRM_PANEL_MIPI_DBI=m CONFIG_TOUCHSCREEN_EDT_FT5X06=m CONFIG_BACKLIGHT_GPIO=m CONFIG_BACKLIGHT_PWM=m ./compile.sh BOARD=orangepizero3 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie Also, with the configurator window open, I selected to enable panel_mipi_dbi Perhaps you still have an image of the assembled Armbian?

Hello, Could you please tell me which image does not have netplan? I want to compare how much resources it uses. Thanks

I'm not sure vulkan is the best solution, RK3588, as most ARM SoCs has a dedicated video engine, vulkan is mainly needed on hardware without dedicated engine, using graphic card to decode, as it's often the case in x86_64 worlld. You can then including it's decoding in vulkan if you want. Don't know wich version of kernel/mesa/video decoder you use. The best, is to remove all dedicated package, and use system one, today, everything work fine with standard linux kernel, as armbian one, standard video tools, rockchip specific libs/video tools was used with rockchip made tools, until everything was mainlined. I don' use VLC, that needs specific libs, but mpv, or several other video players (including firefox one), and everything plays fine.

I dont know how to do that, sorry!

Thanks Robertoj All the documentation for the board is here https://github.com/zharijs/zmxxxp-re But the LCD is not an himax-hx8394. The screen is a "MTF0397SWI-06" using the chip OTM8019A. It just that I am starting from this driver to port the sunxi driver: sl698ph_720p. I will now look at your links.

Tried this with a Ubuntu PC today, and have the same result. lsblk shows one partition.

I followed your tutorial, and it works! I did it with a server image instead. But I was not able to make Wifi work. Did you manage to connect to the Wifi?

Thanks! This fixed the issue!

Try installing qemu-user-static package via apt

Hi again, So sorry to have left this hanging, due to lack of time. I have been trying successive updates since posting this, without the issue being resolved, but have now confirmed that this is kernel or device-tree related. Using armbian-config to load kernels, I can say that the problem originated some time between kernel 6.1.104 (02/02/2025) and 6.6.750 (03/02/25). dmesg output looks similar with and without the problem, as does /proc/device-tree, but I can post any specific output here if anyone can suggest what to look for. 6.6.750 keeps the backlight and a noisy/gray screen, while the screen is black (with backlight showing in the corners) with later kernels, suggesting a further change around 6.12 (tbc) Unfortunately I can't see where to find any armbian intermediate kernels / device-trees, so would be very happy if someone could point me at a repo. where they might be available. Failing that I can try to locate kernels from alternative sources, or compile my own, but it would be good if I could keep as much the same as possible (including any Armbian patches and the armbian dt packages.)

Hi, I'm trying to build the Armbian for Rock64. Host machine is Ubuntu 24.04 AMD64 (but it is running in VirtualBox under Windows). Build fails with the following error: [🐳|🌱] Deploying qemu-user-static binary to chroot [ qemu-aarch64-static during image-early ] [🐳|🔨] '/usr/bin/qemu-aarch64-static' -> '/armbian/.tmp/rootfs-232e77ba-e6ab-4067-8029-afd44bd1d0b9//usr/bin/qemu-aarch64-static' chroot: failed to run command ‘/bin/bash’: No such file or directory [🐳|💥] Error 127 occurred in main shell [ at /armbian/lib/functions/rootfs/distro-specific.sh:276 create_sources_list_and_deploy_repo_key() --> lib/functions/rootfs/distro-specific.sh:276 extract_rootfs_artifact() --> lib/functions/rootfs/create-cache.sh:130 do_with_logging() --> lib/functions/logging/section-logging.sh:81 get_or_create_rootfs_cache_chroot_sdcard() --> lib/functions/rootfs/create-cache.sh:90 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:14 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:208 main() --> compile.sh:50 The /bin/bash (/armbian/.tmp/rootfs-232e77ba-e6ab-4067-8029-afd44bd1d0b9/bin/bash) seems an ARM64 and this might be the reason for "failed to run". Is this a known issue? Can I fix it? I've tried to avoid using chroot in this line, the build goes forward but fails with similar error later.

Furthermore, today I built an Ubuntu desktop PC, and flashed a build onto an SD Card. The resultant installation has only ONE partition. No Windows involvement whatsoever Same with a USB flash drive (to eliminate the SD card adapter). So where do we go from here?

I think I have a partial success but I'm struggling to get anything but white on the red display! Will update when I have more results. panel-mipi is loading, and Card-1-SPI appears under /sys/class/drm/ which is very promising. Verified that /lib/firmware/panel-mipi-dbi-spi is still present, still patched with Kungfupancake's init, and is loaded according to lsmod (as well as dmesg) My current DTS: Edit: I installed XFCE to test, and strangely this has caused dmesg to throw errors related to panel-mipi. I had these same errors when panel-mipi was missing from /lib/firmware but it is still present there.

I tried the edge kernel, but the image became distorted. With extended use, it produced kernel artifacts.

Thank you! I've been unable to give this a crack over the last couple of days, but I'm hoping to try this weekend. I'll post back here with how I go

FWIW, on my rk3588 devices the NPUs are working with recent mainline releases: [ 5.967316] [drm] Initialized rocket 0.0.0 for rknn on minor 0 [ 5.975499] rocket fdab0000.npu: Rockchip NPU core 0 version: 1179210309 [ 5.978652] rocket fdac0000.npu: Rockchip NPU core 1 version: 1179210309 [ 5.985602] rocket fdad0000.npu: Rockchip NPU core 2 version: 1179210309 This script runs the Mesa example with the latest available working versions: And with this script, the Mesa example runs, with a small adjustment, also with the TFLite successor LiteRT: A MediaPipe sample can also be set up easily: But unfortunately, the MediaPipe framework does not support the extended delegate functionality of LiteRT (TFLite). And therefore no NPU support. classification-3.11-tflite.logclassification-3.13-litert.logobject_detection-3.12-litert.log

you may actually want to extract the dtb file on the android side of the tvbox you have just to get the OS to get recognize that chipset (but may not work due to missing driver).The odds for this kind of tv box to have a working wifi chipset is a lottery, most likely you better off not waste that effort and just buy a USB WiFi dongle instead, at least it works far better than a SDIO based wifi chipset like that.

hdmi audio doesn't work with the latest linux kernel 6.16.8 (edge). OS: Armbian Bookworm, latest build (v26.2.0-trunk.32). revert to 6.15.4 helps. Test Output (aplay -l): Kernel 6.16.8 (BROKEN): card 0: Codec [H616 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Kernel 6.15.4 (WORKING): card 0: Codec [H616 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] card 1: HDMI [HDMI], device 0: ahub_plat-i2s-hifi i2s-hifi-0 [ahub_plat-i2s-hifi i2s-hifi-0] P.S. I am using the edge kernel branch because support for the analog audio jack on H616/H618 requires kernel 6.13 or newer. Currently, kernel 6.15.4 is the latest working version that provides both analog and HDMI audio.

I'll try. So far, just booting the board did not work. I suppose it does need mainline uboot. Need to figure out this fdt stuff somehow too...

you need linux kernel >=6.13 (you can use edge kernel)

Wonderful.

Yes. We should add `pahole` as a dependency of the linux-headers package, otherwise during headers install, the `.config` is different from the image build, leading to all kinds of sad. While we might fix the future, unfortunately, installing pahole manually (and removing/re-installing the linux-headers package) is the only way forward for versions already out of the door.

@Mayuyu, Here is the download link for the MiniArch-20231112-6.6.2-board-h313.x96_q-SD-Image.img file. It will remain available for 7 days: https://www.transfernow.net/dl/20251204LnfNp5iz

I have managed to compile the driver on the target with a brand new image compiled using "./compile.sh INSTALL_HEADERS=yes". Yet I would like to cross compile it. If you know how, I will greatly appreciate if you give the method.

I would like to know too. The orange pi zero 3 has a GPU that's available for SIMD acceleration through the latest OpenGLES library, but I haven't had time for that: https://ai.google.dev/edge/mediapipe/framework/getting_started/gpu_support Try it in your opi5+, then run the mediapipe python examples. Then look for other neural network tasks that use the same NN engine: tensor flow light (tensor flow, pytorch will need a different method) Other examples: https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#comment-167001 https://opencv.org/blog/working-with-neural-processing-units-npus-using-opencv/