All Activity

I use ubunta jammy 1.0.8 for desktop, a 32 GB sd drive, and I was able to achieve a new result: the image was recorded (there were problems with the sd card) and now I just have a red light on all the time, and the operating system does not boot, so the image is not displayed on the monitor, no

Hello, can someone help me with Armbian for this Android box, which seems to have a good configuration for a media center? I would like to know how to flash it and which firmware image I can install on it. Thank you. BBox 4K Specifications: Dimensions: 15x15x3.6cm SoC: Marvell BG4-CT Processor RAM: 2 GB Internal Memory: 16 GB 4K – UHD: Ultra HD, for 4 times better image quality DTS and Dolby sound with S/PDIF and HDMI audio output 128 GB TV recorder, to be completed with the media of your choice Connectivity: SD card reader / 2 USB 2.0 ports Wi-Fi Bluetooth

Which image are you using to boot?

Thanks for compiling that overlay in to a DTB - i've just tried putting that in to /boot/dtb/rockchip/rk3588-nanopc-t6.dtb, rebooted, and it successfully booted and used HS200 mode for the MMC! [ +0.015056] mmc0: SDHCI controller on fe2e0000.emmc [fe2e0000.emmc] using ADMA [ +0.006109] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ +0.000031] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ +0.000008] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ +0.000023] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 95,32 bit host data width,256 deep fifo [ +0.000004] mmc0: new HS200 MMC card at address 0001 [ +0.000045] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ +0.000236] mmcblk0: mmc0:0001 A3A444 230 GiB [ +0.002488] mmcblk0: p1 [ +0.000267] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ +0.000759] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ +0.000672] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) I'm puzzled as to why that worked, but the overlay didn't work. I would have grabbed some logs if I could, but there was no display output so I think the only output would have been on the UART? Unfortunately, I bought the version that comes in a case and the UART is on the top side of the board that I can't access. Searching around, it doesn't look like it is easy to pop it out of the case either. Just in case putting it in to user overlays was wrong, I tried reverting to the original DTB, putting the overlay in /boot/dtb-6.12.44-current-rockchip64/rockchip/overlay/rockchip-rk3588-nanopc-t6-emmc.dtbo, activating it via armbian-config, and rebooting. Unfortunately I hit the same issue as before where it wouldn't boot. Is there a way I can debug why the overlay isn't working without getting access to the UART header on the top of the board?

That's already a topic (with a solution): https://forum.armbian.com/topic/55129-trixie-apt-warning-policy-will-reject-signature-within-a-year/

I just updated my odroid hc2 from bookworm to trixie. Everything went find and the system is running. However, I now get the following message from "apt-get update": W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details W: http://apt.armbian.com/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details Using the --audit option I get: W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details A: https://github.armbian.com/configng/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2025-10-06T08:29:30Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. W: http://apt.armbian.com/dists/trixie/InRelease: Policy will reject signature within a year, see --audit for details A: http://apt.armbian.com/dists/trixie/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2025-10-07T19:06:52Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. So a key is missing. Where can I get it? And how to install it? Jürgen

Screenshot is in the original post, it still looks the same now.

Please show screenshots of the selection menu step by step when you are trying to install the OS on eMMC. Show me what you see that I cannot see.

The provider's admin console, to be more precise, I'm sorry.

@werner, thanks for the information and the clarification on my concern in the documentation. This sounds like an interesting project, I do believe I'll give it a try. Again, thank you for the encouragement and the pointers.

Admittedly, I had not tested the DTBO at runtime so far, but only applied it statically to the base DTB and checked whether all desired changes were made as intended. Now I am running my device with the applied overlay and I get the following: [ 0.940862] mmc0: new HS200 MMC card at address 0001 [ 0.941665] mmcblk0: mmc0:0001 A3A561 57.6 GiB [ 0.943039] mmcblk0: p1 p2 [ 0.943767] mmcblk0boot0: mmc0:0001 A3A561 4.00 MiB [ 0.945199] mmcblk0boot1: mmc0:0001 A3A561 4.00 MiB [ 0.946661] mmcblk0rpmb: mmc0:0001 A3A561 16.0 MiB, chardev (506:0) So everything is as expected, and yes, I have ensured that my system is running with the applied overlay. In the past, I have at least once noticed far too late that my system was running in a fallback, and a feature to be tested was not applied at all. That's just the disadvantage of a fail-safe system that only leaves a non-functional system in an extreme exceptional situation. Since you haven't provided meaningful logs, I can't say what is going wrong on your end. To rule out an error when applying the overlay, you could start your system with this DTB (rk3588-nanopc-t6.dtb) , which already contains the overlay applied statically.

Thank you. What do you suggest I do? I'm not sure that the "update bootloader" choices are showing the correct devices either.

What exactly have you installed on the SD card (version, image name), and what steps have you used to install?

same problem， and 25.11.0-trunk.129 img dont work

On 99% of the devices I know, eMMC is initialized in the OS as /dev/mmcblk0, but there are cases when this is not the case. # find real mmcblk device numbered 0, 1, 2 for eMMC, SD for ret in $(find /dev -name 'mmcblk[0-2]' -and -type b) do if [ -b ${ret}boot0 ];then emmc_dev=$ret else sd_dev=$ret fi done This part of the code was implemented due to the fact that on some eMCC platforms there can be both /dev/mmsblk0 and /dev/mmcblk1(2) This works for chips that provide boot0\boot1 partitions to write the bootloader. I think we can add more sophisticated logic to handle this exception for these chips. You can add here the name of the chip on your device. The translation may not be accurate. Please specify if something is not clear.

Hi, I have the same TV Box and would like to install Armbian Linux. Could someone tell me which version to install and how?

I have a TV box with 1.5 GB lpddr3 that has been running Manjaro Arm without any problems for a long time. I used this TV box to add lpddr3 support to the dram driver many years ago. You can get the latest patch for 6GBIT lpddr3 support here: https://github.com/iuncuim/manjaro-h616/blob/main/uboot-t98-h2b-lp3/0007-shrink-ram.patch

moved to tvboxes

From the Circuit Schematic it looks like the Radxa Rock 5B+ RK3588 GPIO0-C0 is the fan I/O, GPIO pin 24, if thats correct. I will verify I can access this on the Armbian distro.

I've installed Armbian Ubuntu Nobble Cinnamon on sdcard with Polytron PDB F1 and it's chipset amlogic S912 After login with lightdm, my screen turn black, What I should do?

Hello, I have two Orange Pi Zero 2 for two years, I didn't know what to do with it. Yesterday I have installed Armbian_25.5.1_Orangepizero2_noble_current_6.12.23. The serial was a bit buggy during installation (display + key press), I have used option -L with screen: screen -L /dev/ttyUSB0 115200 Thank you for your great work !

Hello. I have x96q DDR3 v5.1 box. I flashed vontar h618 image with patched dtb. Everything seems fine except extended file properties. Docker need these properties to operate normally. Can you suggest image with extended file properties support for my box with working ethernet?

Orange pi 5 wifi now supports injection mode using nexmon. Kali distro available from setup menu.

You don't have to run on bare-metal. A proper VM will do too and is probably the better solution. Yes. Cross-compiling is used for everything that's not native. You're aware that the command in the docs is just an example, right?

Armbian does not come with some sort of admin console. Please elaborate. Try different patch cable. moved