All Activity

@Ducdanh Nguyen your box might have secured boot enabled. You’ll need to compile an image with this secure boot patch

Hello @Nick A, i found out my box has verified boot on it, meaning it couldn't boot in other os as you may know, is there any possible way to disable it as soon as i found out my box is not even trying to boot on armbian and with "toothpick method" it showed a fake update screen. I'm so frustrated, couldn't have any way to boot to the sd card and haven't got the dtb too, my box is not rooted. The only last resort is i can see if it automatically boots to it without the "toothpick method"

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

After a lot more experimentation, I have noticed the frames I am missing are the 802.11b ones! So something must be disabling these on Armbian. Unfortunately I cannot find what.

I guess that is a bit misleading. As mentioned using armbian-config is optional to do certain tasks in a more comfortable way than manually/traditionally.

Where did you get that info?

@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

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