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.

/dev/video0 - usually is the camera V4L driver. Cedrus driver usually is /dev/cedar_dev. Also you can see

https://github.com/twdragon/FFmpeg/tree/cedrus264 may produce green line artefact at the frame bottom on 1080p resolution. In the https://github.com/agustinov/FFmpeg-Cedrus/tree/4.4-cedrus this artefact is fixed.