All Activity

Is your rootfs formatted ext4? By bricked you mean, boot would be interrupted, but the brick situation is easily fixable for a skilled technician by doing an fsck?

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

Hi, you can try to set up a readonly root filesystem: https://wiki.debian.org/ReadonlyRoot Cheers

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.

Just to let you know. Rebasing our patchset on top of latest mainline is always a big effort, so getting the latest kernel may be delayed for weeks or month.

Um...no? Where did you get that info? Using armbian-config is totally optional. Everything this tool does can also be done manually.

i've been using armbian for a whole hour now i figure i've mastered this thing :) i loaded Armbian_25.5.1_Odroidxu4_bookworm_current_6.6.88_minimal.img on a sd and fired up an old xu4 according to the instruction the first thing to do is run armbian-config but it hangs because i don't have an interweb connection is there a way around that

You're right - this works perfectly. I'm not typically a Debian user, so I'm not sure where this should be configured in a proper way. But at least I can unleash the CPUs now. Thank you for the very helpful reply.

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]?

Awesome! Thanks so much for this! I see they're addressing some key issues, such as NPU functionality and fixing the ES8388 audio issue with the Orange PI 5 Plus (the board I have). This is terrific!!

Can you please explain what you mean by this ? Am I supposed to install it on the host ? If so, this solution is not working for me. I am trying to compile armbian with docker from arch, it worked a few months ago (commit from February 2025) but now it doesn't (commit from August) Same error as original poster.

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.

This case is a clone of X88PRO: However i use HK1 rom because regular x88pro lack of many features like saf and without this dolphin-emu and others dont allow use external devices another thing added in HK1 rom is cpu thermals, cpu load and memory load in status bar but use this rom make frontal screen in tvbox dont work In my case armbian works using information from this themes: armbian used is based on station-m2 image from here: https://www.armbian.com/station-m2/ https://github.com/armbian/community HDMI - works (need to check hot plugging) HDMI sound - works USB 2.0 - works USB 3.0 - works (using now usb 3.0 hub with power adapter) LAN - Works WLAN - Works SD-Card booting and detection - works RKDevTool installing and loading images on/from eMMC - works GPU - works Hardware video acceleration (except for browsers) - works Dualboot if you flash new bootloader (SD-Card boot high priority) - works Loader* from vontar work ok for use sd boot *For use this follow steps in vontar guide, work ok in dual boot (armbian on sd and android in emmc) sd used is a microdata 64gb from aliexpress (work ok): https://es.aliexpress.com/item/1005007142224952.html rk3566-box-demo.dtb dont recognize usb keyboard but using rk3566-box-demo_x96x6_24_custom.dtb from x96 x6 theme work correctly and hub work on usb 2.0 and on usb 3.0 too also in usb 3.0 port have a 500GB HDD Laptop USB Drive In other things can install xfce desktop, lightdm, xorg, chromium, firefox, nm (for lan), xarchiver, dolphin appimage also can enable panvk using this: VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/panfrost_icd.aarch64.json PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1 from here: Add some images of tvbox, i make a mod (i dont have experience with tools) for add a fan, results are very impressive this tvbox at max stay around 79 to 80 degrees but now with fan stay around 35 to 45 degrees Images from system Dolphin-emu 2506

Hi, First of all, thank You for your work. On a project we are using Nanopi Neo Air boards with an Allwinner h3 processor and a 8GB eMMC flashed with an Armbian OS: $ uname -a Linux <DEVICE_HOSTNAME> 6.6.75-legacy-sunxi #1 SMP Sat Feb 1 17:37:57 UTC 2025 armv7l GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Recently we have been getting increasing reports of the boards being stuck on boot, on message 'Starting Kernel ...' (checked from logs available on COM port). Although this behavior is highly undesirable, since the eMMC is visible in device tree when booting from an SD-Card, it can be recovered by running command $ fsck /dev/mmcblk2p1 In order to reproduce this behavior we have set up a continuous power cycle test where, booting from eMMC: Device is powered on After 70 seconds (enough time for the system to boot), power supply is interrupted Device remains powered off for 10 seconds This would account for around 1000 power cycles per day and we were able to get the device bricked in the range of 68 to 5500 power cycles. We then repeated the test but by booting from an SD-Card and were not able to reproduce the issue, having reached power cycle counts of 34381. Does anyone have a clue on why the eMMC displays this behavior, or is someone able to provide some guidance on what we could do/check to try to prevent this from happening (or making the eMMC more resilient to power cycles)?

@dale I remember wifi stopped working once. You could try this branch and see if it works for you. I haven’t tested it on my x98h yet. On transpeed the a/v audio has issues so I haven’t released images. https://github.com/NickAlilovic/build/tree/v20250407

The deep rabbit hole of (DAS) UBOOT !! This is not for you if you is running on: Internal eMMC with factory Android boot loader. eMMC with updated boot loader but no other boot media. eMMC with updated boot loader and second boot loader and system on SC-Card and no other boot media (Jump booting eMMC > SD-Card). eMMC erased / not working and loading boot loader and system and boot loader from SD-Card and no other boot media, But if you is running on: eMMC with updated boot loader and jump booting to SD-Card with boot loader and booting from there other media. eMMC erased / not working and loading boot loader (and perhaps system) from SD-Card and jump booting other media. Then jump booting on one SD-Card the UBOOT is loading the init system with first stage of the kernel from the SD-Card. If have one compatible second stage boot on the SD-Card and UBOOT is loading it it shall being OK. But as all armbian media have the the same "rootdev=UUID=c6b30a59-8162-46cb-b449-e9615c4a9889" or lable in the armbianEnv.txt on the uboots boot partition its "roll the dice" witch partition the kernel is using then its have loading. If using the SD-Card and its current with the uboot kernel all is OK. But around 50% is using one of the USB media and if its boot partition is not in sync with the kernel its being very strange. If having one SD-Card with latest noble with updated system and kernel 6.16X and putting in one USB-SSD with one old Jammy and uboot on the SD-Card is booting it is the first kernel loading first stage from the SD-Card (sd /boot) and then mapping the system with /boot from the USB-SSD. The result is very interesting then the old Jammy is coming up with 6.16X kernel but cant loading modules that it need after the first stage of booting then the /boot/ is the Jemmy with original system and modules that the 6.16X kernel cant using (but its BOOTING !!!). For booting the system in the right way its possible caging the "rootdev=" UUID or lable in the armbianEnv.txt on the SD-Cards /boot. Its working but you is missing the auto select of boot media = if labling the USB-SSD "SSD" and putting in the lable "SSD" it cant boot the system on the SD-Card or other USB devices (and i think its still getting mixing files from the SD-Card and SSD). Also formatting the XF4 partition on the SD-Card (not touching the partition table) its booting all USB media OK then uboot is using the system and boot form the USB media and only mini loader from the SD-Card. Or if having the same system type / version it shall working updating both the system to the same level and have the same hard and software configured on the SD-Card and the USB system media. Normal symptoms is problem with network manager starting all services, Docker service not starting and other services can having problems. Also if installed kernel and the real booted one is not the same its not good then its being miss match of many files its depends on. I have using the erase and sync method and its looks working OK but the sync is more work but can have more systems working OK as backup if somthing is going wrong. As long our UBOOT cant select / and /boot partitions like in X86 systems wi must living with that but if knowing how its working we can living better with it. PS: some version of armbian-config can force witch media to boot from but i have not testing it and its not in the latest version also i have not testing eMMC with updated boot loader and jump booting then the box i testing it on have failed eMMC so only SD-Card boot = no risk for bricking the system hard and must force mask-rom. So now running Noble with 6.16.1-edge-rockchip64 kernel !!!

I am currently developing an application that requires using monitor mode with RT8821CU chipset (rtw88 kernel driver). Previously I was using RaspberryPi OS and everything worked great, but I am moving to Armbian mainly to be able to target more SBCs. The problem is in Armbian, the WiFi monitoring performance is much much worse (at least with the RT8821CU) than with RaspberryPi OS and with my Arch laptop, and I cannot guess why could this be. I have tested on the rpi4b the following: * Build the rtw88 driver with debug and debugfs enabled just in case. * Test with all the three kernel versions available (edge 6.16, current 6.12, legacy 6.6). None of them achieves decent performance. * Test the 8821cu driver (**a different driver than the rtw88**): seems to have better perf, but doesnt support the fcsfail feature I need and is quite unstable (for example creating a new interface on the device phy using iw, causes the system to freeze and requires a hard reset, and on some circumstances, calling iwconfig also freezes the system). * Try all of the above on the community supported OrangePi 3 LTS: same result, I have the same poor WiFi monitoring performance as with the rpi4b * Cross compile the Raspberry Pi kernel myself (I tried with version 6.6) with rtw88 driver enabled, and manually install it in my rpi4b Armbian SD card (copy the kernel, dtb files and modules, and create appropriate symlinks): I get the same perf as in Raspberry Pi OS! So there must be something with the kernel built with Armbian that is causing this monitoring performance degradation. Unfortunately I am clueless about what could be causing the problem. I have reviewed the kernel configuration, and all options related to the RTW88 driver are the same. But there must be something elsewhere that I cannot find. Any suggestion about what could be the problem or how to debug it? Thanks in advance!

I usually check here every couple of days: https://patchwork.kernel.org/project/linux-rockchip/list/ Yes, they will be included in edge kernel and in a year or two when the next LTS kernel hits they'll be included in current as well.

Thank you @Werner, that makes, sense and I'll follow your advice. Can you please tell me where do you check those updates? And should I assume that when those changes are completed in mainline, they'll make it to the Armbian distribution with the regular updates? Or will I need to change to a different one if noone updates this one? Thank you again. Kind regards

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

@robertoj thank you for the answer. I will look at it. @Nick A Hi Nick, for your x98h box, is the wifi working after a reboot command?

I am observing the same thing. This can be easily fixed by setting the max frequency manually; https://www.incertum.net/post/2024/armbian-cm3588/ I checked `cpufreq-info | grep "available frequency steps"` And made this to set the correct speed for all the cores on the RK3588 NAS KIT # Little cluster (A55 cores: cpu0–cpu3) for c in 0 1 2 3; do cpufreq-set -c $c -g schedutil -u 1.80GHz done # Big cluster (A76 cores: cpu4–cpu7) for c in 4 5 6 7; do cpufreq-set -c $c -g schedutil -u 2.40GHz done Now running `watch -n1 "cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq"` together with `for i in $(seq 1 $(nproc)); do yes > /dev/null & done` shows the frequencies going up correctly, and down too when I `killall yes`