All Activity

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

I did get an alert from BalenaEtcher, when writting the IMG file to SD. It reported not having a BOOT partition. I continued through the alert and the PI board did boot to the prompt results I originally reported. I am going try you image now and will let you know.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.6.1 ~60fps@720p box64 environment variables: Call of Duty 2

Did you get an error when using balena etcher? I tried flashing the image myself and it wouldnt create any partitions. I uploaded an image with a repaired partition table to gdrive and mega. Alternatively, you can use gparted to repair the image yourself. Just put: sudo gdisk /path/to/Armbian-unofficial_26.02.0-trunk_Orangepi4a_trixie_edge_6.18.0.img r (recovery), then d (recreate primary header), then w (write) into wsl or linux.

duplicate https://forum.armbian.com/topic/57200-orange-pi-zero-2w-repeatedly-asks-for-wi-fi-password/?do=findComment&comment=231167

Hello everyone, I am using an Orange Pi Zero 2W with a graphical user interface (GUI). I downloaded and installed the official Orange Pi Zero 2W image. Unfortunately, I keep running into a Wi-Fi connection issue. After booting, the system repeatedly asks me to enter my Wi-Fi password. If I don’t enter it, I have no internet connection. What’s interesting is: If I disable and re-enable Wi-Fi in the network manager, it automatically reconnects to the known network without asking for the password again. Alternatively, a system reboot also restores the Wi-Fi connection automatically. I have already seen online that this seems to be a known issue, but I haven’t found a proper or permanent solution so far. Has anyone experienced similar behavior or knows how to configure Wi-Fi so that it connects reliably and permanently without repeatedly asking for the password? Thanks in advance!

Thats not correct. cedar_dev is the outdated and quite useless cedar driver from alwinner et.al. cedrus is the open source, latest by Paul Kocialkowski, bootlin, which decoding works properly appears and as video1 video2. Encoding has some bugs on H3. I made some progress in fixing but still have lot block artifacts... T.

One last attempt. Reverted back to .62 due to upstream regulator handling changes https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.62_minimal.img.xz

Bummer. Well. Was worth a try. You can stick with 6.18 for now.

Unfortunately I tested both of the images provided and neither worked. After testing the images I ran the commands that were asked to be run on the following images: Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_edge_6.18.2_minimal.img [ETHERNET CONNECTION WORKING] (I realized that forky isn't for me so I compile it with trixie which is used for the official images and it also works) Armbian_community_26.2.0-trunk.151_Orangepi3-lts_trixie_current_6.12.63_minimal.img [ETHERNET CONNECTION NOT WORKING] dmesg | grep -i "phy.*halt\|mdio.*reset" In both images it didn't show any output. watch -n 1 'ethtool eth0 | grep -E "Speed|Duplex|Link detected"' Every 1.0s: ethtool eth0 | grep -E "Speed|Duplex|Link detected" orangepi3-lts: Mon Dec 29 21:48:01 2025 netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device In both images it showed this because Armbian use end0 instead of eth0 so I ran it with end0 instead and it showed this: [Ethernet Connection NOT working image] Every 1.0s: ethtool end0 | grep -E "Speed|Duplex|Link detected" orangepi3-lts: [DATE] Speed: Unknown! Duplex: Unknown! (255) Link detected: no [Ethernet Connection working image] Every 1.0s: ethtool end0 | grep -E "Speed|Duplex|Link detected" orangepi3-lts: [DATE] Speed: 1000Mb/s Duplex: Full Link detected: yes cat /sys/class/net/eth0/phydev/phy_state 2>/dev/null In both images it didn't show any output. I think is because not only is end0 instead of eth0, which I tested by changing them, but also there isn't any phy_state file in the /sys/class/net/eth0/phydev/ directory.