All Activity

Hello there, I recently gained remote access to a Banana Pi F3 to test it, and everything went smoothly. The board was running Bianbu Linux, and I was able to install and use Docker without issues. Now, I'm considering purchasing the board and was wondering if the Armbian image would also support running Docker. Do you have any insights on this? Thanks!

hey, @cmuki! Using the dts from the rk3576-evb1-v10 / rk3576-armsom-sige5 / rk3576-rock-4d in the https://github.com/radxa/kernel/arch/arm64/boot/dts/rockchip/ directory After modification, they can all boot the Armbian version h96-m9s Note: The rk3576-linux.dtsi file forcibly specifies the UUID of the rootfs device partition, which may cause system boot failure. Adjustments might be needed. The basic modification method is simple: disable the PCIe and GMAC1 configurations, modify the reset_pin configuration of GMAC0 to gpio2 and PB3 to enter the system. I used rock-4d as the template for modification. Other modifications have not been thoroughly studied yet.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

hi, ubuntu22 gome desktop How to fix USB sound card with card1 identifier 1

thanks

Have you tried installing qemu-user-static package manually and retry?

Tried a few hours later? Alternativly you can choose a fixed mirror from here: https://docs.armbian.com/Mirrors/

@Nick A oh your build for the Tanix TX6S worked perfectly for me already (thanks!) though I did notice some weird behaviour on my other box that's supposed to be identical to this one. stuff like armbian-config freezing when trying to format the eMMC mainly. I noticed a hang in the kernel in the dmesg when that happened so I suspect there might be some minor difference in the hardware that I'll look into later. for right now I've moved to a box with an amlogic s905y4, which is a whole other can of worms. I got debian-on-amlogic to boot so I'm hoping I can copy over the u-boot and dtb in other to get armbian working on it, since it has more features for SBCs. thanks for your help nick!

@jwillb00 try this build. https://github.com/LYU4662/t95zplus-h618-build

Hi everyone, I'm having trouble recovering my Android TV box T95 Max with the following specs: CPU: Allwinner H616 RAM: 4GB ROM: 32GB Board: AXP313A V3.0 The box was freezing after boot, so I tried to reflash the firmware using PhoenixCard / suit. What I’ve Tried So Far: Downloaded and flashed T95-H616-A27.img & T95-H616-A29.img through FEL mode and Flashing completed successfully but the box only shows a black screen on both HDMI and the small front panel screen. Tried other firmware images labeled for T95 Max H616 AXP313A Tried re-burning the SD using different cards and readers I found a working Armbian img that worked from SD card: https://github.com/NickAlilovic/build/releases/download/v20240716/Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz I want to restore the TV box to a working firmware (Android 10 or 12) if possible. And is there any method to revive bootloader if it's corrupted Any working image file would be a huge help. Board Image attached:

I'm on the most recent Armbian 25.2.3 Noble version. When I try the command $ yes | sudo apt dist-upgrade I get the following error: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: ... Learn more about Ubuntu Pro at https://ubuntu.com/pro The following upgrades have been deferred due to phasing: gnome-shell gnome-shell-common ubuntu-drivers-common The following packages will be upgraded: thunderbird 1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 68.6 MB of archives. After this operation, 453 kB of additional disk space will be used. Get:1 http://apt.armbian.com noble/noble-desktop arm64 thunderbird arm64 9:128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1 [68.6 MB] Err:1 http://apt.armbian.com noble/noble-desktop arm64 thunderbird arm64 9:128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1 File has unexpected size (68620562 != 68620660). Mirror sync in progress? [IP: 2a01:4f9:3b:4943::2 80] Hashes of expected file: - SHA512:e49ee18c96333c4dfbb188458a3fb8ce271874d1aaf830ce4aed2ff5b3f59220cc4ead01243323047a6d7ef7258b6f2f66f5d231ea83dfc53356e4d9aeeef0d6 - SHA256:581efd7ac140c5c416648efad6fcea96ed4cccc9db6e8300b6200860399d9f5c - SHA1:de05de93f62cf5b298bddbdc65fcb95fe0c4062e [weak] - MD5Sum:91c1809c8ca059ebdfb71787b02f3b4b [weak] - Filesize:68620660 [weak] E: Failed to fetch http://fi.mirror.armbian.de/apt/pool/noble-desktop/t/thunderbird/thunderbird_128.10.1+build1-0ubuntu0.24.04.1~mt1armbian1_arm64.deb File has unexpected size (68620562 != 68620660). Mirror sync in progress? [IP: 2a01:4f9:3b:4943::2 80] Hashes of expected file: - SHA512:e49ee18c96333c4dfbb188458a3fb8ce271874d1aaf830ce4aed2ff5b3f59220cc4ead01243323047a6d7ef7258b6f2f66f5d231ea83dfc53356e4d9aeeef0d6 - SHA256:581efd7ac140c5c416648efad6fcea96ed4cccc9db6e8300b6200860399d9f5c - SHA1:de05de93f62cf5b298bddbdc65fcb95fe0c4062e [weak] - MD5Sum:91c1809c8ca059ebdfb71787b02f3b4b [weak] - Filesize:68620660 [weak] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? It seems like some checksum or some other validation data doesn't match the actual data. Thanks for any guidance on this matter.

Hi, sorry to bother you again. I recently tried to use latest Armbian 25.2.2 Bookworm and unfortunately 10mbps mode is not working. I suppose there is a regression. @brentr May I kindly ask you to have a look again at this topic? Cheers

These forums are for Armbian Linux issues. This is not the place to ask for android firmwares.

Hello I am using a Debian 12 VM on Qubes OS 4.2 to attempt to build an Armbian image for a Rockpro64. As you can see by the build logs, these 3 commands are failing: update-binfmts --enable qemu-arm update-binfmts --enable qemu-aarch64 update-binfmts --enable qemu-riscv64 Then arch-test command output causes script to error out with: arm64: not supported on this machine/kernel So far I have attempted to enter the docker container and manually run the command but I get this error: root@1631353b980f:/armbian# update-binfmts --enable qemu-arm update-binfmts: warning: qemu-arm not in database of installed binary formats. update-binfmts: exiting due to previous errors Any help is greatly appreciated as I continue to try solving this, thank you!

Good afternoon everyone. I need your help. I have an Android TV Box TX9 and I need the ROM (Firmware) for it because I can't find it anywhere. Could someone help me download this firmware so I can resurrect my device? Thank you all.

As long as the board isn't dead it is starting to boot. That is why Werner directed you to how to capture the uboot booting messages via a uart connection to the board.

How do I get a log if the OS won't evenstart to boot?

yes, next week should arrive CH340G, will check with it

@jwillb00 I’m using miniarch patches with my build. This is kernel 6.12. I also have 6.14. When I have time I’ll update to 6.15. https://github.com/NickAlilovic/build/tree/v20250306/patch/u-boot/u-boot-h616 https://github.com/NickAlilovic/build/tree/v20250306/patch/kernel/archive/warpme-6.12

In this second article of a three-part series, I look at how Matt Godbolt uses modern C++ features to try to protect against misusing an API that deals with destructive state transition based on a talk he gave on making code easy to use and hard to misuse. View the full article

I don't know particular about this board so I can only give generic clues and hints how to help us helping you. What kind of dependencies you mean? There is uboot only. For variables and boot script check the contents of /boot Power loss is not an issue. Most that can happen is corrupted rootfs.

ok how i fix it? go next: sudo find /boot -type f -name '*cs0*dtbo' i see on next: rk356x-spi<BUS>-m<MUX>-cs<CS>-spidev.dtbo │ │ │ │ │ │ │ └─ номер Chip-Select (0 или 1) │ │ └─ «mux» — какие именно ноги вывели наружу (m0, m1…) │ └─ номер аппаратного SPI-контроллера (spi0…spi5) └─ серия SoC (rk3566 / rk3568 = rk356x, rk3588 …) next setup instruction: | Шаг | Команды (копируйте строка-в-строку) | Что должно получиться | | | ------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------ | ---------------------------------------- | | 1. Перейти в домашний каталог | `cd ~` | | | | 2. Создать исходник DTS | `nano rk356x-spi3-m0-cs1-spidev.dts` | вставьте текст снизу → **Ctrl-O, Enter, Ctrl-X** | | | 3. Скомпилировать в DTBO | `dtc -@ -I dts -O dtb -o rk356x-spi3-m0-cs1-spidev.dtbo rk356x-spi3-m0-cs1-spidev.dts` | файл *.dtbo* рядом | | | 4. Узнать каталог оверлеев | `export OVR=/boot/dtb/rockchip/overlay` | (у вас именно такой путь) | | | 5. Скопировать файл | `sudo cp rk356x-spi3-m0-cs1-spidev.dtbo $OVR/` | | | | 6. Проверить | \`ls \$OVR | grep cs1\` | увидите *rk356x-spi3-m0-cs1-spidev.dtbo* | | 7. Убедиться, что в `/boot/orangepiEnv.txt` есть строка | `overlays=spi3-m0-cs0-spidev spi3-m0-cs1-spidev` | если всё ок — дальше | | | 8. Перезагрузить | `sudo reboot` | | | | 9. После ребута | `ls /dev/spidev3.*` | **/dev/spidev3.0 /dev/spidev3.1** | | #6 can be ignored. at #2 next: rk356x-spi3-m0-cs1-spidev.dts <=== name code: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3566"; fragment@0 { target = <&spi3>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; spidev@1 { /* CS1 = регистр 1 */ compatible = "spidev"; reg = <1>; spi-max-frequency = <10000000>; }; }; }; }; sudo reboot after this: ls /dev/spidev3.* orangepi@orangepi3b:~$ ls /dev/spidev3.* /dev/spidev3.0 /dev/spidev3.1 make like

Ok this happened again and I'm out of ideas. @Werner Could you tell me the dependencies for the boot process on this board and how I could read out the values like the boot loader to verify they are still the same? There should be nothing wrong with cutting power right? I have had raspberry pi's be cut from power daily for years without issues and I assume it would work the same for the odroid boards?!

@deskwizard I don't know why I refer to OPi5Max, maybe I had other tab/topic open or so, but it is clear that it is about the OPi5. Now I have the ROCK5B, just cloned the Armbian Bookworm from ROCK3A but did not write SPI yet. Power up with fixed 12V in USB-C and from SD-card with Armbian rock5b vendor U-Boot. rootfs from NVMe, SATA overlay enabled for 3.5inch HDD. 5 audio cards: root@rock5b:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiphdmi0 [rockchip-hdmi0], device 0: rockchip-hdmi0 i2s-hifi-0 [rockchip-hdmi0 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchiphdmi1 [rockchip-hdmi1], device 0: rockchip-hdmi1 i2s-hifi-0 [rockchip-hdmi1 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: rockchipdp0 [rockchip-dp0], device 0: rockchip-dp0 spdif-hifi-0 [rockchip-dp0 spdif-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 4: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card3 (unlisted) is HDMI-input I think, but disabled all in KDE settings tray except the 3.5mm plug ('headphones'). No further settings or volume change, mpv playing an mp3 instantly. I will likely do/test with 6.15 edge, also maybe 6.12 current (and other U-Boots as well). But first several mechanical/cooling things to tweak, need to drill/cut a hole for the SATA connector in the cooling metal I think.

hello guys, i hawe question, my device: orangepi 3b 8gb OS: 1.0.6 Jammy with Linux 5.10.160-rockchip-rk356x 3.3V → 3.3V → PIN 1 GND → GND → PIN 6 SCK → SPI SCK → PIN 23 MOSI → SPI MOSI → PIN 19 MISO → SPI MISO → PIN 21 SDA → CS → SPI CE0 → PIN 24 =========================== /boot/orangepiEnv.txt ``` verbosity=1 bootlogo=true extraargs=cma=128M overlay_prefix=rk356x rootdev=UUID=4b3309b6-9bbe-431d-8609-82360b5b6154 rootfstype=ext4 overlays=spi3-m0-cs0-spidev spi3-m0-cs1-spidev ``` orangepi@orangepi3b:~$ ls /dev/spidev* /dev/spidev3.0 <================= only one... cant add new spidev 3.1 and more.. for connect another mrfc522 how to fix?