Active threads

For the Orange Pi Zero v1, it might be recommended to upgrade U-Boot to version v2025.4. I remember having similar problems with the Orange Pi Zero 3, and after the U-Boot update, the reboot works correctly and doesn't shut down the computer.

I see that the reported problem was raised in another topic:

There is certainly nothing planned. In general most of the open source community has moved away from working on amlogic based devices as the support from amlogic if lacking (and given the arm cpu space where all arm cpu vendors don't really support main line linux very much, amlogic is significantly even less supportive). So these days around armbian in particular most developers choose to invest there volunteer time in Rockchip cpus (and more recently some in allwinner cpus). But this is open source and community driven. So anyone is welcome to pitch in and do the heavy lifting to support it if they want. That is how most boards get support, is that someone with an interest volunteers to do the work.

Okay that detects 1.5gb at spl, but then detects 2gb at uboot, just like the first patch I tried. Maybe something to do with me currently using the U-Boot DTB from X96-q, a 2gb device? I did try a different config for a different tv box as well (transpeed), but that had the same result. U-Boot SPL 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) DRAM base address is defined as 0x40000000 DRAM has 15 b/raw, 10 b/col, 4 B/width, 2 #rank and 8 #bank DRAM top address must be less than 0x80000000 DRAM top address must be less than 0x60000000 DRAM: 1536 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.14(debug):armbian NOTICE: BL31: Built : 15:34:29, Aug 13 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 DRAM: 2 GiB (effective 0 Bytes)

Yep, I’ve been testing the 1.5GB version with Armbian. Images are still rough—some issues with AdGuard Home not starting properly after reboot, and a few quirks with networking. Promising board though, especially for the price.

The Mesa 25.2 release introduces support for AFBC compressed YUV textures in the Panfrost driver for ARM Mali GPUs, enabling more efficient memory bandwidth and power usage in video playback and real-time texture processing. View the full article

https://github.com/NickAlilovic/build/releases/ [01.296]secure enable bit: 1 I see this in your android log so I believe you have to enable secure boot. If the images don’t boot. These are the steps to enable secure boot for tanix_tx6s_axp313. (Link below) [01.303]PMU: AXP1530 You have a axp313a so transpeed, x98h and tanix might work for you. [359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) Transpeed, x98h and tanix use ddr3 If emmc or wifi do not work. You can use your android dts to find the gpio numbers. You might also need to take a picture of your wifi chip.

I am using Orange Pi Zero2 / Zero2W / Zero3 boards with the Allwinner H618 SoC and I am encountering an issue with I2C3 (mv64xxx_i2c). Board Details: Board: Orange Pi Zero2 / Zero2W / Zero3 SoC: Allwinner H616 Kernel: 6.12.35-current-sunxi64 (Armbian) Overlay: i2c3-ph (/boot/armbianEnv.txt: overlays=i2c3-ph) Pinout: PH4 = SDA, PH5 = SCL Problem: After boot, /dev/i2c-2 is created, but the bus is locked dmesg shows: [ 0.846937] i2c_dev: i2c /dev entries driver [ 1.479459] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.484185] /soc/i2c@7081400/pmic@36: Fixed dependency cycle(s) with /soc/pinctrl@300b000 [ 1.501006] mv64xxx_i2c 5002c00.i2c: Error applying setting, reverse things back [ 1.501095] axp20x-i2c 1-0036: AXP20x variant AXP313a found [ 1.502779] axp20x-i2c 1-0036: AXP20X driver loaded [ 53.381005] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 55.429017] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 Attempting rmmod: sudo rmmod mv64xxx_i2c rmmod: ERROR: Module mv64xxx_i2c is not currently loaded Bus /dev/i2c-2 remains locked System Information: Full system info collected via https://paste.armbian.com/vezeminihu What I have tried: Created a new overlay i2c3-ph for PH4/PH5 Configured /boot/armbianEnv.txt to load the overlay Rebooted multiple times, but the bus remains locked Verified pull-up resistors (PH4/PH5 connected to 3.3V) Questions: Has anyone encountered mv64xxx_i2c bus lock on H618? How should DTS / pinctrl / PMIC be adjusted to get the bus working? Is there a working example overlay for I2C3 on Orange Pi Zero3 / H618?

I have installed AdGuard https://docs.armbian.com/User-Guide_Armbian-Software/DNS/#adguardhome on a clean Armbian bookworm on some Rockchip device running vendor kernel. Boot logs: https://paste.armbian.com/hibaporove.yaml Reboot and AdGuard normally works after: https://paste.armbian.com/enomawupip.yaml It could be some SD card issue. Try - different one. If you didn't use Armbian install method, then check system logs to see what is failing ... Armbian is Debian or Ubuntu from userspace perspective, so it could be some AdGuard install issue.

I'd do it in a 'simplier' way, just use a new uSD card, that is partly a benefit of SBCs running on uSD cards.

Thanks for your feedback. But as I wrote, it looks like hw accel works in general when checking the much lower CPU load vs. the fps. CPU 4x100% => ~10fps HW 1x20% => ~6fps Thats why I think the VPU really gets used but not optimal. btw. I did not yet get mpv to work with frambebuffer. T.

Short GPIO PIN13 and PIN14

Thank you so much for your generosity, @coroner21. I shall do my very best to keep the machine well maintained in Armbian.

Start reading here..

Getting the grub bootloader right with tow-boot's efi implementation seems like the most urgent as it is a hard blocking anyone trying to install. As tow-boot isn't unique to pinebook pro my guess is that handling it impacts other systems. I don't know what would be involved in maintaining it.

hello everyone! I bought this tv box..https://www.aliexpress.com/item/1005009346784515.html?spm=a2g0o.order_list.order_list_main.11.79e81802pgNRxu but after starting it was not possible to log in to googleplay even though I had a connection via wifi or ethernet. the preinstalled version for applications was Aptoide TV..through it I wanted to update all applications (youtube, netflix, etc.) I managed to do that but no application could be started. the original file manager did not show the internal memory or USB disk or SD card until I managed to download ES file manager through aptoide and it showed my flash disk I installed HW info device and there I found out that it was an RK3528 chip. so I wanted to flash the firmware and I used a rom image for H96max with the same parameters. the firmware upgrade went OK but the device is dead. I can't find the correct firmware. I'm attaching a photo--- maybe someone will recognize the board and identify which rom-img should be correct. the seller can't help me in any way.

@Thiên Thư Lục USB3 is little half working and i have USB-3 HD/SSD and its freezing some times but normally Armbian is running stable on it. Also general devices in the USB3 jack is freezing like SDR dongle stop being recognized then being pullrd out and in agenand need one repower of the box for getting the USB3 jack working agen. The factory Android bootloader is not supporting USB boot only SD-Card or eMMC . Write one updated / new on the eMMC (can soft bricking the box) or erase the eMMC shall doing it then the chip is loading it from the SD-Card if not found eMMC. Also putting in one SD-Card with updated boootoader and it shall being possible "jump starting" to USB devices like sticks and HDs from the SD-Card.

yep, thats how i connected them i think it might be that? ill try to get some fresh wires and see if it helps

I also confirmed that USB-C functionality is still not working on ODROID-M2 with Kernel 6.16 RC. I guess we would have to wait a little more for the working USB-C Port.

Depending on your location this might not be anything that can be fixed on Armbian side. If this happens on any mirror, the issue is either your setup or ISP blocking access.

THANK YOU

I get this warning because I removed lightdm-gtk-greeter.desktop... what should I do to not expect the file? roberto@orangepizero3:~$ update-alternatives --display lightdm-greeter update-alternatives: warning: alternative /usr/share/xgreeters/lightdm-gtk-greeter.desktop (part of link group lightdm-greeter) doesn't exist; removing from list of alternatives lightdm-greeter - auto mode link best version is /usr/local/share/xgreeters/pi-greeter.desktop link currently points to /usr/local/share/xgreeters/pi-greeter.desktop link lightdm-greeter is /usr/share/xgreeters/lightdm-greeter.desktop /usr/local/share/xgreeters/pi-greeter.desktop - priority 70 After some research of greeters, I see that the default greeter is compatible with wayland https://github.com/Xubuntu/lightdm-gtk-greeter I have been working as if lightdm requires X11 (which I need to avoid), and so I wanted to used pi-greeter Does anybody have lightdm+gtkgreeter in a pure wayland setup? No X11

If I remember correctly, it is possible to mount such partition flashed to usb or sd within WSL (just ensure that proper support is installed into WSL) and make any changes. It is possible even to script changes to be run under windows, though I can't remember how exactly this is done. Probably AI can hint.

I have an old and weak mxq pro 4k TV box (fake amlogic s905w), rk3228a checked, sv6051p wifi. I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like that,this is off topic, but please help me fix this, I definitely need linux to make a server for the telegram bot.

Try SharpExt4Explorer: https://github.com/nickdu088/SharpExt4Explorer