Active threads

Use the provided curl command at the end of every build run or use "SHARE_LOG=yes" with the compile command to auto-upload. Nobody will try to read through this unformatted mess.

Easiest way is to use the customize-image.sh file in userpatches. Stuff there gets executed within chroot on the sdcard just before its closed and assembled. More advanced way is using extensions. Check extensions folder for examples.

You can either experiment with the CLEAN_LEVEL switch or use kernel-patch or uboot-patch (depending on what you want to modify) to create proper patch files from the diff.

Try change the folder permission, chmod -r 775 /home/odroid/

Did you download stretch already, before I remove it to put up Bionic?

@Nick A I woke up and i'll start working on it.

Hello, everyone. I'm using Armbian_25.5.2_Orangepizero3_bookworm_current_6.12.30-homeassistant_minimal on 4GB OpiZero3. When booting from sd, the bluetooth controller is initialized correctly. I made a boot from usb-ssd via armbian-config: everything works fine, but the bluetooth controller is not initialized. /sys/class/bluetooth is empty. Switch back to sd - it works again. Boot from ssd - no. I compared whether it transferred the distribution correctly from sd to ssd - all files are the same. What could be the problem?

This looks normal. Most of those boards have bootloaders at locations prior to boot partition. Boot loop. This can be many things - i would guess kernel crash and watchdog issue restart. Why that happens? Hard to tell. This way? sudo screen /dev/ttyUSB0 115200 It should prompt out something.

Hi, I used to run a full docker environment using the Radxa Debian buster image upgraded to bullseye. Lately as the backport repo has been archived I decided to move onto Armbian as upgrading bullseye to bookworm did not boot (or seemed so...). After flashing the latest Rockpi4 image to the Rockpi4, I copied the docker configuration and files backups. I now have a akward behavior: - starting all the stacks (or containers) works fine, all seems ok - rebooting via sudo reboot provokes an endless reboot cycle which is only ended if I unplug the USB Zigbee coordinator key. Once the loop is stopped, the RockPi does not have any IPv4 address (only IPv6) and is unreacheable by SSH. - power cycling with the USB key unplugged fixes the boot loop and everything is back to "normal", except the following dmseg errors: rock@rockpi4b:~$ sudo dmesg -l 0,1,2,3 [ 3.099273] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.099333] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 [ 11.200510] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 11.731680] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 11.732234] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84 [ 99.980012] cpu cpu4: _set_opp_voltage: failed to set voltage (825000 825000 1250000 mV): -6 [ 99.980072] cpu cpu4: Failed to set regulator voltages: -6 [ 99.980097] cpufreq: __target_index: Failed to change cpu frequency: -6 [ 246.811985] cpu cpu4: _set_opp_voltage: failed to set voltage (825000 825000 1250000 mV): -6 [ 246.812046] cpu cpu4: Failed to set regulator voltages: -6 [ 246.812070] cpufreq: __target_index: Failed to change cpu frequency: -6 [ 400.087329] cpu cpu4: _set_opp_voltage: failed to set voltage (825000 825000 1250000 mV): -6 [ 400.087387] cpu cpu4: Failed to set regulator voltages: -6 [ 400.087410] cpufreq: __target_index: Failed to change cpu frequency: -6 Now this is where it gets strange: if I prevent zigbee2mqtt container to automatically start at boot (which cannot be a permanent solution obviously) it doesn't matter if the USB key is plugged in or not (whichever usb port), Armbian boots ok and all other containers start ok. I already checked the /dev/ttyusb0 access rights, tried to change the docker container user, activate the rockchipdw3 overlay, changing the USB port for the Zigbee key, switching from rolling to stable and vice versa, to no avail. No need to say that the same config worked under bullseye. Does someone have any lead or clue about what's happening ? Where can I look as logs don't show anything special... Any help would be greatly appreciated, thanks in advance! My config: Rockpi4B, Armbian_community_25.11.0-trunk.70_Rockpi-4b_bookworm_current_6.12.43_minimal.img, usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus

Hello and thank you for sharing your experience. https://github.com/redrathnure is the maintainer of your board. Not sure if he is active here in the forum.

Plus the kernel source is getting pulled from their repo. If they did make a change, you should see it on Armbian.

Thank you @Werner, for letting us know and for your efforts

What U-Boot version is used for eMMC resp. SD-card?

it appears to be a useful application is there a way to use it without a network

@Nick A it has same issue. I thik it is related to the device tree declaration. Should it be something like this? https://github.com/LYU4662/aic8800-sdio-linux-1.0

R-TV Box S10 – I realize this is an older topic, but I’m trying to fix an S10 box for an old colleague.. After an update, it no longer boots, stuck on the startup animation, and won’t load Android. I can’t seem to find any firmware download. Thanks in advance.

I looked a little closer and the included cpufrequtil init script is totally unaware of SoC clustering. If you put in a max value for the A76, it won't work for the A55. So I threw the problem into AI and asked for a flexible SoC solution (I'm of course simplifying it). This is what it gave me. Lightly tested: per cluster governors, per cluster min/max speed, ability to specify "min" and "max" rather than numeric values. cpufrequtils-default -> /etc/default/cpufrequtils cpufrequtils -> /etc/init.d/cpufrequtil YMMV. cpufrequtils cpufrequtils-default

Yes. Installing this package on Debian-based build hosts fixed the issue. I don't think we have any developers using Arch so there aren't much tests of any other distros to ensure compatibility. Main focus is on Noble. If there is an equivalent package for arch try installing on the host machine and retry. Having it inside the docker container may not be enough.

that’s a super specific and annoying issue! It sounds like Armbian is still exposing an A2DP (audio) profile even after you tweaked the main.conf. Have you tried disabling the audio sink entirely via Bluetooth CLI or modifying the /etc/bluetooth/audio.conf (if it exists) to set AutoConnect=false under [General]?

Hi. I have Rock Pi S0 boards that I install in an enclosure. It works, but it is conceivable that some critical bug or change with the image is discovered in the future so that customers later need to flash a new image to the emmc. But for them to do this, they would have to open the enclosure and locate the maskrom button, very inconvenient. Is there a way to trigger rebooting into maskrom from software instead of pushing the button? Apparently this is possible on the official radxa OS image by running command "reboot loader" instead of just "reboot", but not on armbian it seems. After investigating I see linux patches made by the rockchip team for kernel modules like “syscon-reboot-mode” and from the code I see something like that it’s supposed to write the value 0x5242C301 to the RK3308’s GRF OS register 0, and I guess this is supposed to be read by the bootloader to direct the boot to bootmask mode instead of the OS? But the armbian distribution is already built with this kernel module by default, and I even tried to manually write this value to the appropriate registers and then rebooting, and yet nothing works, it just boots to Linux like usual. Anyone have any ideas?

Thanks for sharing your installation. Really, the Rockship in TV BOX seems the easier Armbian installations that I already tested, although, I use a TVBOX with ab AMLOGIC S912.

Which version or image is that ? From here ? https://joshua-riek.github.io/ubuntu-rockchip-download/boards/rock-5b-plus.html 5.10 kernel or 6.1 kernel? As already indicated, 'images' usually do have a too big scope for identifying the core issue for flaky boot or crashes etc. Also the Armbian '25.5.1' and '25.2.2' are just a text in some file. For my installations that have been always in-place upgraded, they are wrong anyway. Stating buster when I just did reboot into upgraded trixie for example (NanoPi-NEO). W.r.t. PCI-E, and other specific Rockchip HW, 5.10 (legacy) likely has best support. At least for my ROCK3A, I then have RPi camera V1 support (not tested but required overlays are missing in 6.1). Also w.r.t. the earlier mentioned PCI-E NVME+SATA issue, I got it working by merging the Radxa 5.10 ('latest') kernel + Radxa U-Boot '2017' with some Noble userspace from around December 2024. Now Bookworm by the way as I don't want netplan.io. In a running system (NVME working), you could run 'sudo lspci -vv' and look at Capabilities. When non-working NVME, so boot from SD-card and maybe SPI empty or disabled so only the U-Boot from the SD-card is used, it also might give hints. At least I see that SSD can do 8GT/s 4-lane, while RK3588s (NanoPi-R6C) then has to use 5GT/s 1-lane. It is 6.16.1-edge kernel with EDK2-UEFI v1.1 in eMMC. I don't understand all items, but at least some, w.r.t. power-save (ASPM) among those.

Hello In the past I installed armbian into emmc (a95xf3-air) with a USB key. All was ok. Now I would like to do a fresh install with the current release : I burned the image, make the changes (extlinux …) Boot with the "toothpick" method, ssh , the armbian release is the old one from the emmc, not the recent from the key. How is it possible to boot with the recent one with ssh (no display no keyboard) ? And after copy the new release to emmc. Thanks for help

Not sure for what you need it but here: https://github.com/u-boot/u-boot tag specification and defined patch sources are here:

Get the microsd card mounted in your linux laptop Open /boot/armbianEnv.txt Add the line: extraargs=plymouth.enable=0 disablehooks=plymouth https://wiki.archlinux.org/title/Plymouth When you get booted in your armbian OS: sudo apt remove plymouth