All Activity

Just to add, Armbian boots upto systemd and then gets stuck at loading some scripts. This image gives some additional information.

Hi, So, Previously this massage (No emmc) appeared if the preinstalled Android was able to boot up completely and then restarted by repowering while the sdcard was inserted or the tvbox was rebooted while the sdcard was in the slot, however this got fixed if the device was powered off during the android bootanimation but after accidentally installing an incomplete image of latest armbian release I am no longer able to get the emmc working even after trying restarting at various boot levels. I have found others experiencing the same issue in this post but according to the circumstances I am in I think my issue might have a different solution. Any way through which this issue can be solved ? This might help : root@multitool:~# dmesg -T | grep mmc2 [Tue Jan 6 21:06:28 2026] mmc_host mmc2: Bus speed (slot 0) = 2343750Hz (slot req 400000Hz, actual 390625HZ div = 3) [Tue Jan 6 21:06:28 2026] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [Tue Jan 6 21:06:28 2026] mmc2: Card stuck in programming state! __mmc_switch [Tue Jan 6 21:06:28 2026] mmc2: error -110 whilst initialising MMC card I have also attached the whole dmesg log and lsblk output if needed. multitool-ssh-output.txt

I guess the image was built from a pending pull request for testing before merge. Since it has been merged now it should work. Make sure your framework clone is up to date (git pull).

@Werner can you please tell how did you built this image: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Radxa-cubie-a5e_trixie_edge_6.18.2_minimal.img.xz ? Image I get with: ./compile.sh build BOARD=radxa-cubie-a5e BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie seems to be far away from your result. First and foremost it does not boot 😉 I ask because of two reasons: - I'd love to be able to build myself an image that I'm running. - I need to be able to mount ZFS volumes. I'm unable to install `zfs-dkms` and `zfsutils-linux` when using your image. `apt` says that kernels newer than 6.14 are not supported. I'd also appreciate any tips or resources that would help me to get 6.12.x (or whatever lower than 6.14). I experimented a bit but without luck. I saw that it seems that `current` branch should not be supported on radxa-cubie-a5e board but I somehow got an image that at least has 6.12.63 in its name. It doesn't bring much because it does not boot.

Oh, I understand. Camera, hardware video decoder and hardware video encoder - they all appear now as /dev/videoX devices, because new hardware videocodec accelerator driver (or standalone video decoder and video encoder drivers) became V4L2 kind of driver. Also thanks for the reference link.

The ffmpeg conversation in https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 suddenly stopped 2 weeks ago. Does it seem like there's a big obstacle suddenly, or just a well deserved engineer vacation going on?

How did you apply dgVoodoo2 ? I download the archieve file it is a bunch of dll.

Thank you for testing my instructions I was on vacation, and I didn't remember to check this until now Which LCD are you using? Which kernel driver are you using for it? All the questions in your post depend on the LCD model and the driver you used. (I am using panel-mipi-dbi, which I know that it has lost its ability to display X11 graphics since a few months ago) Can you 100% say that you don't have X11? You don't need to use the same kernel version I use. The newer version you have is preferable 🆗 I am glad you can use the Trixie labwc. Personally, I am using Bookworm in the meantime, since its the only way I know to get H264 hardware acceleration. With Trixie's labwc, do you ever get desktop crashes when you log out?

I updated my patches to the new style (using series.conf) and that took some time. They are back online, as are some new images. I post more updates at the opi discord btw. As far as I know, neither network, spi flash or pcie are working currently.

Current way of installing is as written on the download pages. It was verified with latest v24.11.2 image.

I'll try to explain in some details. 1. Yes these are different things even if they appear all as /dev/videoX devices. In case of camera, hardware video decoder and hardware video encoder one may have /dev/video0, /dev/video1 and /dev/video2 2. no, because really the DRIVER does the encoding or decoding provided there is codec hardware present. The driver provides the userland communication to the hardware. This happens through the v4l2 layer (Video For Linux 2) which does the abstraction for different types of hardware, eg. H3, Hantro, Intel ... Of course this requires a v4l2 kind of driver, whereas the cedar_dev (aka cedar_ve) is NOT. 3. Right, bootlin is a little more 🙂 I mentioned these because they provide the latest cedrus driver with encoding support (with still some bugs...) 4. yes, cedar IS outdated. The most modern concept is v4l2 (see above). Cedar and this specific ffmpeg fork are using a different approach. 5. I never mananged to get this combination to work, at least not on the latest kernel. HTH T. Reference: https://bootlin.com/blog/open-source-linux-kernel-support-for-the-allwinner-v3-v3s-s3-h-264-video-encoder/

when send command poweroff or reboot alywas display client_loop: send disconnect: Broken pipe instead in on ArmBian Debian 12: Connection to 192.168.1.12 closed by remote host. Connection to 192.168.1.12 closed. but maybe on Debian 13 now is different message after reboot or poweroff

# cat /boot/armbianEnv.txt verbosity=1 bootlogo=true console=both extraargs=cma=256M overlay_prefix=rockchip-rk3568-hk fdtfile=rockchip/rk3568-odroid-m1.dtb rootdev=UUID=0a9f09a7-bbb5-493f-a7af-b0e62f4aff8e rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u It seems the UUID can be changed in `/boot/armbianEnv.txt`.

@Ducdanh Nguyen, virtually every adapter will work. I'm using DFRobot multiplexer v.1.0 (FT232R-based): https://wiki.dfrobot.com/Multi_USB_RS232_RS485_TTL_Converter__SKU_TEL0070_

During installation new Image show on screen following problems: Failed to retrieve unit state: Transport endpoint is not connected _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v26.2 rolling for Orange Pi Zero running Armbian Linux 6.12.63-current-sunxi Packages: Debian stable (trixie) Support: for advanced users (rolling release) Failed to retrieve unit state: Transport endpoint is not connected trying reboot: root@orangepizero:~# reboot Call to Reboot failed: Connection timed out

I found a way to install 25.04 onto emmc with no problems afterwards. Updates and upgrades just fine now. https://pastebin.com/DzNYtmQa

Looks like stuff got lost due to force-push. Check this how it looked before: https://github.com/rvdr/build/activity?ref=spi-nvme-patches

Okay we're randomly poking at things. Please provide the following for every image you test. dmesg | grep -iE "stmmac|sun8i|dwmac|emac|phy|mdio|motorcomm|yt8531" dmesg | grep -i "registered.*phy\|phy.*connect" ls -l /sys/bus/mdio_bus/devices/ cat /sys/bus/mdio_bus/*/phy_id 2>/dev/null find /sys/class/net -name "end0" -o -name "eth0" | head -1 | xargs -I {} cat {}/phys_switch_id 2>/dev/null ls /sys/firmware/devicetree/base/soc/ethernet*/mdio/ and the output of armbianmonitor -u (if network doesn't work use -U instead to print to stdout) The following one adds phy-io-supply = <&reg_gmac_3v3>; to the emac, just in case... https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.63_minimal_phy-io-supply.img.xz

@Sergey LepeshkinThanks for the clarification. Could you please recommend a specific USB-to-UART (3.3V TTL) adapter model that you know works well with this TV box? A product name or chip (CP2102 / FT232RL / CH340, etc.) would be really helpful.

Thank you Nick, great work - best overall image so far for the A7Z a733 board. I'm experimenting with 13M imx214 radxa camera - how to get correct device tree for your image? I see that imx214 module is compiled, but CSI interface configuration seems to be missing.

mpv has the correct code to use the ffmpeg for cedrus hardware acceleration AND the correct code to display it on screen with minimal CPU usage. If you want gstreamer as a video pipeline, can you try using ffmpeg (the v4l2request version) and gstreamer together?

@Marvin-03 Looks like your GIT no longer has the changes for OrangePI4a board available.

Unfortunately, it didn't work.

Ok, maybe, I have not enough or outdated information. Could you help me to understand latest changes and correct me? 1. I think, camera driver and codec video engine driver - are different things, because there are completely different hardware: CSI video input and videocodec accelerator. 2. I think, video engine driver and video coding software with special codecs - are different things, because a driver does not encode/decode video, it only gives access to videocodec accelerator. And video coding software (app or lib) is not a driver, but uses a driver to get access to the videocodec accelerator. 3. So is it really driver performs video decoding in bootlin? Also, as I understand, bootlin - is not just a driver, but big project with it's own Linux, alternative to Armbian, with builtin specific driver and libs. Can I install bootlin driver on Armbian? 4. Doesn't previously mentioned https://github.com/uboborov/sunxi-cedar-mainline use /dev/cedar_dev path? Is it outdated? 5. About encoding on H3. FFmpeg-Cedrus (https://github.com/agustinov/FFmpeg-Cedrus) maybe is outdated, because uses /dev/cedar_dev, but seems to encode without lots of artifacts.

@Marvin-03 ** run the commands to fix partitions on my IMG build, just like you mentioned and it fixed it.** Your Orangepi4a img is working, I am able to BOOT. But I am accessing the board through the console. Confirmation of the boot is below. I also had a look at the partitions from the IMG created of the GIT build and your own image. See details below. This is the partitions list of the IMG build of GIT This is the partition list of your IMG for comparison