All Activity

I have tested them and they don't work that much 😞 The kernel is too old, Linux kernel 6.12 lacks many existing mainline patches in 6.14, but even with 6.15 (current development) the board lacks support for the wireless chip or the NPU. For sure one day the board will work with mainline kernel, but it's not now, currently Vendor 6.1 kernel works the best for the board.

I’m using an Android TV Box X96 X6. Right now, I want to find a way to install Armbian on it, but I haven’t been able to figure it out yet. I’d appreciate any help or guidance from the community.

Thanks everyone, I will change the forum branch.

I have been able to fix this issue for myself. It ended up being the case that the USB-C to USB-C wire that I was using would work as USB3.0 on the Zero3E in a specific orientation only (which is weird because it works every which way on other devices) So what I did was I kept flipping the typeC port on both the Zero3E side, and the external SSD until it was detected as USB3.0, and then I marked those with sides. Now, I just look at the markings to check which sides of the cable need to be facing upwards and connect it to the Zero3E and the external SSD, and its never gone to USB2.0 mode again! Super weird issue, and an even weirder fix I must say. P.S. The cable works in USB3 mode in any orientation on all other devices, it's just this way with the Zero3E, and I have no clue why!

apparently it needs libheif https://github.com/libvips/libvips try apt-cache search heif apt install libheif1 alternatively, there is libavif https://github.com/AOMediaCodec/libavif I'm using libavif, built that from source, but you can nevertheless try sudo apt install libavif15 libavif-bin libavif-dev

I have a big problem with the latest Armbian images, the problem not only persists with the latest versions, with the previous one the same thing happened to me with the old Ubuntu images, it works without problems with the old kernel, I have a video published with the problem since it works but at certain times the device turns off and does not turn on a single LED light until I reconnect it, I thought it was a problem with the power supply but not with the old Ubuntu images it works and even with the game emulators of the lakka-tv image, so I came to the conclusion that the hardware is in good condition, therefore check what the fault could be because the computer usually turns off. I leave the link of the video it is in Spanish, sorry . HARDWARE: Banana Pi M1

Can someone who has NanoPi M6 confirm this issue? I'm not sure if it's a software problem or is my NanoPi M6 has a defective hardware.

So, I'm got this "old" TV BOX as a gift, and I'm try to do something with this ... Now I have booted image for Odroid C1 (after 2 or 3 days work) Req. HW mod: - two resistors / wires for working console are needed - pics later HW & SW info: TV Box Name: Sencor SMP 5000PRO CPU: amlogic meson8b (s805 ??) Armbian build file name: Armbian_25.2.1_Odroidc1_bookworm_current_6.12.13_minimal.img.xz DTB file used: meson8b-odroidc1.dtb Kernel Version:6.12.13 Distribution Installed: bookworm Working Ethernet (Yes/No):??? Max Ethernet Speed that works: 100 Does wifi work (Yes/No): ???? Does bluetooth work (Yes/No):NO ?? Does HDMI audio work (Yes/No): It is Androind TV box, 1GB RAM, NAND flash 8GB, 1x LAN, WiFi, 2x USB 2.0, HDMI, SDcard slot, IR, 2 color status led, audio jack, Android 4.4.x I can provide some rom files, from stock android, or whole nand. and (maybe) need some help with this .. (thats all for this midnight)

There are multiple threads discussing RK3566 support on TV Boxes in this forum. You should read that content first if you haven't already.

It looks like your box is Rockchip RK3566 based, moving to the Rockchip TV Box sub-forum

Armbian is assembled from Ubuntu or Debian packages. If problems is there, problem is here too and there is little we can do about. https://docs.armbian.com/#what-is-armbian We have a mechanism which you can use to insert patched package to our repository, which is in use in some corner cases: https://github.com/armbian/os/wiki Perhaps this is a solution, perhaps not depending on possible dependency nightmare.

@greg396 You can downgrade linux to 6.6.87: unzip the file debs-6.6.87.zip on your helios, cd into the folder and submit 'dpkg -i linux*'. With linux 6.12. I get some timeouts during data transfer. You need to install the modified dtb for the linux-6.6 branch in /boot/dtb/rockchip/ (do not forget 'update-initramfs -u' after that and reboot). Follow the link load distribution and Install the code displayed ('cd ... exit 0') in /etc/rc.local and reboot. I have disabled any Armbian updates by commenting the text in /etc/apt/sources.list.d/armbian.list but submitting 'apt-mark hold armbian-firmware' may work as well. However, I have no idea whether or not OMV requires a specific kernel branch - but I don't think so. If you need to reinstall linux 6.12. you can collect the three corresponding deb packages (linux-image, linux-dtb and linux-headers) on http://beta.armbian.com/ (currently 6.12.25).

moved

Dear ebin-dev, the rtl_nic firmware from your link are already in /lib/firmware/rtl_nic - anything I should do? the modified dtb for 6.12 are installed already in march - without any changes. Your suggestion should be to downgrade the kernel, but how can I downgrade from actual kernel 6.12.x to your recommended deb-package 6.6.87 without getting into trouble and how I should disable kernel updates?

Whenever you are comfortable with that. You could brick your box. Unlikely, but there are so many different tv boxes out there that there is always a chance your box is somehow different than common ones. Since the boot environment starts from what is on emmc, if you screw up the emmc completely, your box is bricked. (You should still be able to recover by using amlogic tools to reinstall an android rom, but...) No limit that I can think of. You have that all correct.

I’m using an Android TV Box X96 X6. Right now, I want to find a way to install Armbian on it, but I haven’t been able to figure it out yet. I’d appreciate any help or guidance from the community.

guys, any noob-friendly guide to make JL2101 ethernet work by editing dtb ? i did : dtc -I dtb -O dts -o rk3556-h96-tvbox.dts rk3556-h96-tvbox.dtb but that's all what i know, i dont know which string should i change in the dts file before converting back to dtb or is it currently not possible to make it work without full armbian rebuild instead of just modifying the dtb file ?

Hi @Ed van den Enden, Checked a bit more on the internets and found that you have added the device overlay to your BanananaPi in the same manner as you have done on your RaspberryPi: dtoverlay=i2c-rtc,ds1307 On armbian you add overlays using: # armbian provided overlays overlays=usbhost2 usbhost3 i2c0 uart1 pps-gpio # user provided overlays user_overlays=rtc0-i2c-ds3231-rtc1-soc Also confirmed that boot.cmd indeed only expects to see user_overlays in the armbianEnv.txt and does not check for dtoverlay. You can check in /boot/dtb/overlay/ which armbian provided overlays are there, but for the i2c RTC you would need to add a user defined overlay. Safest bet would be to use the armbian-add-overlay tool that will compile (and check) then add the overlay to your armbianEnv.txt using the keywords that will make sure the overlay is used during boot. As mentioned before as well, you would need to have the device tree files handy for armbian-add-overlay to process them. These are .dts files and are human readable. The topic mentioned in the reply earlier has the two .dts device tree overlays that should also work for your case. Groetjes,

I have the latest revision of the armsom sige 5. This board has an updated Wi-Fi chip set. It was changed from RTL wireless to a Broadcom chip connecting to the rk3576 with SDIO 3.0. I grabbed the latest Armbian image and it appears in the device tree It is still referencing the RTL Wi-Fi device. has anyone encountered this and found a solution? Or has gotten Wi-Fi working? I’ve attached the device tree. sige5.dts

I have got my T95Z Plus with S912 booting 6.12.24-current-meson64 just fine now. Getting Jellyfin up and running with all my old DVDs and CDs. Seems very capable. When do I push the OS into the eMMC? Is there a downside? Are there only so many times I can do this safely? If I chose to try the Debian builds - don't I just boot from a SD card and try it out? If I like that one better - then don't I just repeat the process and push that onto the eMMC? I believe I have the Android Source - or more precisely - I have a rom called SuperCelleron that I installed almost 10 years ago... That still boots when I don't have an SD card in. Also - visual inspection of this board proves I have an eMMC. I have another box that is identical outside. But on the inside it clearly has a NAND chip. I am sure this is a silly question - but just thought I'd ask. Thanks all.

Here's the steps to create a secure boot image git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build pico patch/u-boot/u-boot-h616/153-add-tanix_tx6s_axp313_defconfig.patch You need to add this line to the bottom. "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" and change "@@ -0,0 +1,37 @@" to @@ -0,0 +1,38 @@. diff --speed-large-files --no-dereference --minimal -Naur u-boot-sunxi-647b392bf20614006917d5fcd3390347a668eee5/configs/tanix_tx6s_axp313_defconfig u-boot-sunxi-647b392bf20614006917d5fcd3390347a668eee5/configs/tanix_tx6s_axp313_defconfig --- u-boot-sunxi-647b392bf20614006917d5fcd3390347a668eee5/configs/tanix_tx6s_axp313_defconfig 1970-01-01 01:00:00.000000000 +0100 +++ u-boot-sunxi-647b392bf20614006917d5fcd3390347a668eee5/configs/tanix_tx6s_axp313_defconfig 2023-04-08 11:53:13.408413187 +0200 @@ -0,0 +1,38 @@ +CONFIG_ARM=y +CONFIG_ARCH_SUNXI=y +CONFIG_DEFAULT_DEVICE_TREE="allwinner/sun50i-h616-tanix-tx6s-axp313" +CONFIG_SPL=y +CONFIG_SUNXI_DRAM_H616_DDR3_1333=y +CONFIG_DRAM_CLK=648 +CONFIG_DRAM_ODT_EN=y +CONFIG_DRAM_SUN50I_H616_UNKNOWN_FEATURE=y +CONFIG_DRAM_SUN50I_H616_BIT_DELAY_COMPENSATION=y +CONFIG_DRAM_SUN50I_H616_READ_CALIBRATION=y +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x03030303 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x00001c12 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x00000001 +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0000c05 +CONFIG_DRAM_SUN50I_H616_TPR2=0x00000000 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f0007 +CONFIG_DRAM_SUN50I_H616_TPR11=0xffffdddd +CONFIG_DRAM_SUN50I_H616_TPR12=0xfedf7557 +CONFIG_MACH_SUN50I_H616=y +CONFIG_R_I2C_ENABLE=y +CONFIG_SPL_I2C=y +CONFIG_SPL_I2C_SUPPORT=y +CONFIG_SPL_SYS_I2C_LEGACY=y +CONFIG_SYS_I2C_MVTWSI=y +CONFIG_SYS_I2C_SLAVE=0x7f +CONFIG_SYS_I2C_SPEED=100000 +CONFIG_PHY_REALTEK=y +CONFIG_SUN8I_EMAC=y +CONFIG_I2C3_ENABLE=y +CONFIG_AXP313_POWER=y +CONFIG_USB_EHCI_HCD=y +CONFIG_USB_OHCI_HCD=y +CONFIG_USB_MUSB_GADGET=y +CONFIG_SUPPORT_EMMC_BOOT=y +CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x40 +CONFIG_MMC_SUNXI_SLOT_EXTRA=2 +CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y pico patch/u-boot/u-boot-h616/secure-boot.patch create the secure boot patch. diff --git a/root_key.pem b/root_key.pem new file mode 100644 index 0000000000..892a10ef90 --- /dev/null +++ b/root_key.pem @@ -0,0 +1,28 @@ +-----BEGIN PRIVATE KEY----- +MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQCWZ7G39E+RCi+9 +B48yiD4GxnfqNzvlXOxAd+GHQuKbgynXZd5pIuNHt3ewhZTHZkdHxuO9liqX9MmU +8OhiG+Skww2LzHPPi/eLeN4vCt/waXkjFrkblkhNzB3c6MejKdiz9sfw8oeOFX1S +teP/MJBoRaj6Hexj5g/oCspU+KFfv0cOBcWuq4vZwPJ6+U44IBi7EGleShGHNhBI +xQEyvNaDLWoDCPGLrjRM0DrIbUpzEntk9KJ0z+3Th8O/FtvlW21atolIVr5F96Pw +EEv3CDUHrY+IvK0z+IwNhnYo99kMPi5djB6vviz4In530JQ+OdPxhi4cQY3Yw9wx +Sm8EFaRRAgMBAAECggEAEaEcZ+k7VU8aGuBStNPa31zui9XHD8KlT4YtuXbJzHwi +kKSYXf7woISdAyQZNQkkREHICn4aRn7zDOHy/yLxWS2ivhbsITDxBlhXxLBT4OBg +ClCcyGLEXVgWTQE8+z9Jrwh3VaL76BfVPXdj/tKwroQxwwV0Yp5CEYsIPc75zVjW +Y2tppJL9XlTfKXTSo7FAxJmjkTC8QGPSHgMglR5FOfZ/D3Nj4KV4LV1gHCkICKUy +c2jklHISy8S6/pvgpWb50TKArEhbN6uAKQBNb74ZsChKJ9h9aof/vjH/8Ab1rwUJ +g91lpkR3mEefTjJTW1JOuoT49Y3lfWmkRVh75GiCsQKBgQDUo3uMcy9VdbbmY9Gt +2JuhbSvwR/dOHZJoXvtlNYVJ+1JvavExBy2u31cYsK/2SH/Upc8AXS6H02dXbnC3 +wjlUFi21Xi7/PCQM8TUz05km3+9qOkDYw53EBBBnCdjawBpDgcUSkoZGU+ltBzcR +sj0nsmI29DjwfYHXhofnlfI52QKBgQC1E2Q0hGfk3YUtfzTjDJCfd3gs6QYGQGeT +49jvnsbYsnz9vsK4Ao2skN8nBhSefDJR8h2X+7tRXEefQB2Hy/+9qoiuoVzPJGWD +IiHjeVJDoEqA2Q483UhZ+OPjUGFDTI7O/j1A1HkEBKswdJpKlGVygdoXYaieUAfz +Sb+dCYf7OQKBgQCWkE/aSnE4vQpOJl4BEABbFFdpYzvcpxnVJ3Qw3O3NTdS4Keww +wBl72o7sX6eo5vsE0oc5hcF90ZY6FWxg4XkAblfdNZxng+ku9NisIuct3KDFAgyK +sDCU7B/FJfbUJfQy2r91gCTtxVripZo7wI6G/kuHB/UNbIE04AB5XfZPOQKBgAGw +K5f9wAY3Nn2lGPYg8Nw7vegVSBQY155eWnBpd4sfpuCqvZ//jhiUxS/U865ClCmF +a1c2ZpmslZJbg6r3cOvwwhN2t6nKuhON5uj7AZRV0zv+Sg6xNXJ5So6c+jspZI9z +eVi4YmRyMrJh8+pMFeIKaeEb7PmE334aKuoo45apAoGBAKNp7ssXgU4Ma7cUr7+L +TKGBNVsMZyM3T2qsXJjFY1f90+lwp7TlNQGVMPOSOHxyINWkuLNgAgetlhavnc0S +0l+SbSaO6SfnHfQWBFPEJfol8V/Xa4rcVP7fGxQn4phYnk14N09xKIQa24Mi2Xa5 +9G0C2VOB8Yz6OWcQZELs0uFp +-----END PRIVATE KEY----- -- 2.34.1 ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "tanix-tx6s-axp313" choose "edge" rest is up to you. Your image should be in output/images directory.

I would love to use Armbian Build to construct a Debian 12 Bookworm images with KDE Plasma as the windows manager. I note that KDE Plasma isn't an option in the armbian builder. I have no problem building with XFCE or Cinnamon.

moved

Can AVIF support be added to LibVIPS? It works fine on the amd64 version of Ubuntu 24.04, so I'm assuming Armbian needs to update the package. Current bug: Failed to process avif file version: unable to call heifsave_target heifsave: Unsupported compression It's not a HEIC image, this is how LibVIPS encodes AVIF files.

Hi greg396, solutions for your issue were discussed in the parallel thread: You need to update the rtl_nic firmware in /lib/firmware/rtl_nic and use the modified dtb for stability reasons. If there are any remaining problems, check the load distribution on your helios64 and the connection to your client. The iperf3 transfer speeds from helios64 to macos clients in our network are 280MByte/s without any dropouts (linux 6.6.87 is recommended), upload speed is around 230MByte/s and we are using it 24/7 without any issues.