Active threads

moved to tvboxes

moved to tvboxes

https://drive.google.com/file/d/1vyQGR8kgzhCzmwuXhb8q5j707U9IXFob/view?usp=sharing The file in this shared link is the image file provided by the manufacturer for my Android device. I hope it will be useful, and thank you for your help! I can't compile a custom Armbian image and hope to get help from the community.@Hqnicolas

Just for posterity. fluster-run-odroid-m2-summary

Did you also install the dtb that belongs to that kernel version? You could check if the dtbo is compatible with your dtb with: fdtoverlay -v -i /boot/dtb/current.dtb -o /tmp/test.dtb your-overlay.dtbo It would be better to compile the dts with armbian-add-overlay your-overlay.dts so it will automatically install it to /boot/overlay-user and added to your armbianEnv.txt. In this way it also won't get overwritten when you update the dtb. And of course like Werner said, check the debug serial console, you'll see much more detailed information. And check if the symlinks are correctly linked to your kernel version. ls -l /boot

It's more than a year later - but the update to the distro-agnostic.sh to copy resolv.conf also fixed my native build as well. DNS for the apt/image build process was failing before I did that.

I have that line also: [ 0.496136] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to enable supply: -517 [ 0.938478] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier 2-0042 for /power-management@fd8d8000/power-controller/power-domain@8 [ 1.224290] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to enable supply: -517 [ 1.237338] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier 2-0042 for /power-management@fd8d8000/power-controller/power-domain@8 [ 1.294276] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier spi2.0 for /power-management@fd8d8000/power-controller/power-domain@12 [ 17.384495] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba4000.video-codec [ 17.385477] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdba8000.video-codec [ 17.386457] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdbac000.video-codec [ 17.387427] rockchip-pm-domain fd8d8000.power-management:power-controller: sync_state() pending due to fdc40100.video-codec But VPU seems to be working anyway:

I have now built the module with the armbian build framework and then it works.

Hi, just to give a maybe final feedback on this topic: Although it is not a really satisfying solution, I decided to switch off the sysrq functionality by setting kernel.sysrq=0 in /etc/sysctl.conf. This was 1 month ago and there were no sysrq events in my logs since then. So for now this is a "good enough" solution for me. Thank you all for your support, I learned again a lot ...

@blackc Exact the original U-boot DRAM settings from your boot.bin or an update. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 If you are still having issues ask the sunxi guys on IRC. https://oftc.catirclogs.org/linux-sunxi/2025-11-14

I am an Linux Beginner and I only can use Terminal for copy/paste issues. For many months my Raspberry Pi 5 runs perfectly with Armbian. But when I try to update the system in the Discover App, I get the following error message: The following packages have unmet dependencies: kpim6-akonadi: Kollidiert mit: knotes but 4:24.05.2+p24.04+vstable+git20240705.1500-0 is to be installed Kollidiert mit: kpim6-akonadi-notes but 4:24.08.3+p24.04+vstable+git20241129.1417-0 is to be installed Can someone please help me to get my system up-to-date? Thanks in advance!

Armbian Bookworm 25.8.1. (minimal) Odroid XU4 with 32GB eMMc After lots of searching and trying 2017 Hardkernel solutions and github etc - And this forum suggestions - I could never get get it to boot. I think this is partly because things have changed since 2016/17. I did not have my eMMc on an usb adapter. Just installed, brand new (untouched from China) eMMc and a imaage install on MicroSD of Armbian. The method I believed should work was "armbian-install". But, it had errors while using mkpartimage. I put debug statements in the script and found the particular instance of invoking mkpartimage. Actually the issue is; 2 files are missing from /boot folder. Current SD installation image of Armbian minimal only creates one fdisk (MBR) partition on which /boot is a folder. I tried for ages to create a separate /boot partition. Maybe, since I have now succeeded with an eMMc install, I might try doing a separate root and boot. The 2 missing files are armbianEnv.txt and boot.cmd If one "touch"es armbianEnv.txt then - if it doesn't exist it will be created - if it does then no harm done. If one copies boot.ini to boot.cmd then these two things will satisfy armbian-install. Amrbian-install correctly changes the R/O of mmcblkXboot1 (where X is emmc device number) write the boot stuff and markit back R/O. It also ensures that armbianEnv.txt has got correct entries in it. In summary Install eMMc and Micro SD in XU4 Ensure SD/eMMc switch set to SD and boot armbian from SD Login as root or use sudo touch /boot/armbianEnv.txt cp /boot/boot.ini /boot/boot.cmd armbian-install choose the install and boot from eMMc option shutdown change switch to boot armbian from eMMc boot

Hi @djurny Just to inform you that, after cleaning out some mess I made, your overlay and armbianEnv.txt update to make the external RTC ds3231 to work, did the job. For my SBC's I use the Banana Pi M2 Zero and v25.5 rolling for Banana Pi M2 Zero running Armbian Linux 6.6.75-current-sunxi My application needs to work in the field as an Access Point with an RTC, the right date and time is important info in the diagnostics of my applications. A remark on the mentioned Armbian release: For using the GPIO pins of the SBC, python3-libgpiod works great. I use USB camera's (V4L2 camera). After any update or upgrade, my USB camera's won't work anymore. Not really a problem for me, because I'm happy as it works right now, no updates or upgrades needed. Thanks again for your great help. Met vriendelijke groet, Ed

https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rp5.csc https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rpmini.csc You can build images on your own. https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained

Using odroidxu4. flashed Armbian_25.8.1_Odroidxu4_noble_current_6.6.102 to eMMC After odroidxu4 started, followed instruction to create accounts etc. Installed xfce4 package reboot. odroidxu4 booted to console prompt Installed xfce4-goodies package reboot. odroidxu4 booted to console prompt Installed lightdm reboot. The system becomes stuck at plymouth-quit-wait.service/start Not much I could do after this as I could not look at log messages or use $ sudo systemctl status lightdm.service Any insight greatly appreciated Thanks

Choose install/update bootloader on spi flash option on armbian-install. Some uart logs could be useful if you have usb-ttl converter stuff

Hello all, I have a/m model with 2GiB RAM / 16GiB eMMC- Wifi: XR819 (XRadio XR819). I've download and install a .img file Armbian_community_25.11.0-trunk.437_Tanix-tx6_trixie_current_6.12.47_minimal.img.xz I want to have a server version CLI, but I don't know where to find that. My problem is that the WIFI is not availible after the boot in ARMbian. Is there any solutions for make it availible? Thank you in advance.

moved

@Sergey Lepeshkinok

I did not detect the fancontrol issue sooner as I had not tested the trixie image. Indeed PrivateDevices=no should be set because helios64 and helios4 points fancontrol tu /dev symlinks prepared via udevs rules to sysfs files. I don't know if I can get rid of these udev rules, ie if I have persistend access to the proper sysfs directories for thermal and hwmon required by fancontrol on helios64. I also question why only 3 boards uses fancontrol in armbian. I had a thermal policy patch for the dts, it has the added bonus that it works when the kernel start and until it stops thus no uneeded high fan speed before fancontrol start and after it stops. But I am still wondering why kobol team chossed fancontrol and thus what are the pros and cons of fancontrol vs dts thermal policy. https://github.com/armbian/build/pull/8928 PR to set PrivateDevices=no when one upgrades armbian-bsp-cli-helios64-current or edge is in the pipe.

Yes I was able to build a lib which helped me with CEC

Hello everyone, As I said, previous post, I’ve been trying to enable I²S audio output on my Orange Pi Zero 2W (Allwinner H618) using an external PCM5102 DAC, but so far the kernel does not recognize any sound device. I read that the driver sound/soc/sunxi/sun4i-i2s.c supports the H6, and “going” (posted March 4) suggested trying: compatible = "allwinner,sun50i-h6-i2s" to trigger that driver, since the H618 I²S block might be similar. Overlay compiles successfully using armbian-add-overlay and loads on boot. However, after reboot: dmesg | grep -i i2s dmesg | grep -i pcm aplay -l → aplay: no soundcards found... Could anyone confirm whether this driver can handle the H618 I²S, or if kernel patching is required to make it work? Any advice or example DTS overlay for H618 + I²S would be very helpful. Thanks in advance for your time and for the excellent work on Armbian Jose Cardoso

Ah! was that simple huh. Thanks vidplace7! Got it to work once i removed the image on the flash. But I have to put it in maskrom mode if i want to use the SPI in the future which is a pain. Ah well it is fine Also lsusb now works root@luckfox-lyra-zero-w:~# lsusb Bus 001 Device 004: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter Bus 001 Device 002: ID 1a86:8091 QinHeng Electronics USB HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hello, I have a problem after update on strong leap s1, it is stuck at the android tv loading screen, I found this method (1) Mecool KD3 Stick recovery reset | XDA Forums . Basically because this box doesn't have reset button, this method is can be used to get into recovery mode from where you can factory reset the box. Problem is that it's not working for me, is there anyone with same problem ? How did you solved it, please ? Thanks

# TV Box X88PRO13 My TV box is the X88PRO13. It is equipped with the RK3528 chip. I successfully running Armbian on the box. Find How To build and create Image for this BOX on http://github.com/joilg/x88pro A ready to go iso image is on https://github.com/joilg/x88pro/releases/tag/0.3 ------------------------------------------------------------------------------------------------- ## For those who have a different TV Box with RK3528 CPU, try the following procedure: The USB 2.0 and HDMI interfaces are the same for most boxes, so the console output should also be posible over HDMI here. 1. Flash MMC with the x88pro image and insert it into the box's MMC slot. 2. Connect a monitor via the HDMI interface. 3. Connect a USB keyboard to a USB port. 4. Power on the box. 5. In most cases, boot messages appear on the monitor, ending in a login prompt. 6. Follow the instructions on the monitor. ## 7. Extracting the correct DTB file binwalk /dev/mmcblk1 | grep -i "Flattened device tree" This should give output something like this: 67451654 0x4053B06 Flattened device tree, size: 99077 bytes, version: 17 67550731 0x406BE0B Flattened device tree, size: 99112 bytes, version: 17 138280448 0x83DFE00 Flattened device tree, size: 99112 bytes, version: 17 143958080 0x894A040 Flattened device tree, size: 379 bytes, version: 17 143960064 0x894A800 Flattened device tree, size: 99078 bytes, version: 17 Select the row with the largest size value. Replace the placeholders in the following commands: - `<TV_BOX_NAME>` with your box's name - `<START_ADDR>` with the first number from the selected row - `<SIZE>` with the size value from the selected row Extract the DTB file with: dd if=/dev/mmcblk1p2 of=rk3528-<TV_BOX_NAME>.dtb skip=<START_ADDR> count=<SIZE> bs=1 Copy it to boot directory: ```bash cp rk3528-<TV_BOX_NAME>.dtb /boot/dtb-6.1.115-vendor-rk35xx/rockchip/ # or cp rk3528-<TV_BOX_NAME>-android.dtb /boot/dtb-$(uname -r)/rockchip/ ``` Edit the `armbianEnv.txt` file: sed -i '/fdtfile=/c\fdtfile=rockchip/rk3528-<TV_BOX_NAME>.dtb' /boot/armbianEnv.txt sync and reboot your box. Now test if LAN, Audio, IR Remote Control, RTC ... is OK. Wifi is only implemented for the AIC8800 Chip. ### optional convert dtb file to readable DTS source file:: dtc -@ -I dtb -O dts -o rk3528-<TV_BOX_NAME>-android.dts rk3528-<TV_BOX_NAME>-android.dtb ## Additional notes I only have a X88PRO13 box, so I 'm not be able to test whether this works for your device. But it might be worth a try. ### all in one Script #! /bin/sh ## Note:** Replace all placeholders (`<TV_BOX_NAME>`, `<START_ADDR>`, `<SIZE>`) with your actual values. dd if=/dev/mmcblk1 of=rk3528-<TV_BOX_NAME>-android.dtb skip=<START_ADDR> count=<SIZE> bs=1 cp rk3528-<TV_BOX_NAME>-android.dtb /boot/dtb-$(uname -r)/rockchip/ sed -i '/fdtfile=/c\fdtfile=rockchip/rk3528-<TV_BOX_NAME>-android.dtb' /boot/armbianEnv.txt dtc -@ -I dtb -O dts -o rk3528-<TV_BOX_NAME>-android.dts rk3528-<TV_BOX_NAME>-android.dtb ``` ## contribute please report if you have success or anny problens. please contribute also Info to your box, embedded chips (wifi,RTC) and publish your DTB or DTS file.