Everything posted by Werner
- Build failed: "chroot: failed to run command ‘/bin/bash’: No such file or directory"
- Adding the edge kernel to Rock 2F/2A
- Orange Pi Zero 3 Sound Problem(Lineout-Analog Codec)
- Low performance on N2 if kernel version 6.17+
- Adding the edge kernel to Rock 2F/2A
-
Xiaomi Mi tv stick 4k - Quad-Core Cortex-A35 (Amlogic S905Y4)
moved to tvboxes
-
New 'Armbian 25.11.1 Trixie Minimal / IOT' image is possibly corrupted
just noticed current kernel is broken. I assume because of upstream changes. looks like similar what I've fixed for meson64 6.18-rc7. Got it, will send pr Of course this does not explain why the image wasn't correctly assembled at all... Looking good: https://paste.armbian.de/ohagifufem ls -l|grep Odr -rw-rw-r-- 1 root root 142 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.sha -rw-rw-r-- 1 root root 19751 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.txt -rw-rw-r-- 1 root root 322026836 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.x
-
How to install armbian in h618?
Because this is not Armbian. This is a fork which uses the name Armbian without permission. We do not support 3rd party forks.
- FS corrupted after burning image to SD card
- FS corrupted after burning image to SD card
- State of support for Raspberry Pi 5
- USB3 Port Issues on Radxa Zero 3 (Armbian vs. Vendor Builds): USB hub fails, upside-down speed bug
- hi, any info about Qualcomm Dragonwing SoC ??
-
State of support for Raspberry Pi 5
When support for Raspberry Pis has been added there was no model 5 yet. With the intention to only support the flagship the board configuration was added as rpi4b.conf. Since then support was extended across all models from 3 and up. However renaming a board config file is an issue. I already had the idea to address that but gave up on it: https://github.com/armbian/build/pull/7881 tl;dr: rpi4b image will work on all models from 3 to 5. https://www.armbian.com/rpi4b/
- Radxa Cubie A7A/A7Z - Allwinner a733
- Java always crash on OrangPi 5 pro
-
Check and fix filesystem
No. This fork uses the name Armbian without permission and they do not contribute to the core development process. Instead they trick you into thinking that you'd get any sort of support here at our place whatsoever.
-
Check and fix filesystem
You are not using Armbian but a fork. Ask where you got the image from. We don't support 3rd party OS.
-
how to unbrick h96 max m12 amalogic s928x
We don't deal with Android here. Ask vendor or at some place like xda developer forums.
- Trixie/Rock 5B+ - Can't burn it on my nvme drive
- Trixie/Rock 5B+ - Can't burn it on my nvme drive
- Trixie/Rock 5B+ - Can't burn it on my nvme drive
- Trixie/Rock 5B+ - Can't burn it on my nvme drive
-
Is it possible to enable VENC (hardware encoder) support in kernel for S905X3
We don't support 3rd party forks. Ask at the place where you got this OS from.
-
Should i choose the Orangepi over the Raspberrypi?
Because they sell you the hardware only. Their software support is very poorly made since for the price they cannot afford proper software support and - even more important - maintenance. They leave this burden to - mostly unpaid - random developers across the world like us. At least I'd go for a device with Standard Support which the Ultra and Max hasn't: https://www.armbian.com/download/?device_support=Standard support For the raspberry you would need additional hardware (an AI kit I guess). No clue though about how they both perform in comparsion. For RK3588 you have two choices for now: The rockchip bsp implementation and https://github.com/rockchip-linux/rknn-toolkit2. Or using 6.18 kernel using the reverse engineered Rocket driver and latest bleeding edge mesa to get npu access. I personally did not play with either of these options and have no intention to do so for the moment.