All Activity

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.

/dev/video0 - usually is the camera V4L driver. Cedrus (sunxi video engine) 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.

@Marvin-03 Here are the results of the commands provided, hope this help. Thanks for the link of your image builds, will try them out.

Can you test these commands in u-boot? mmc list mmc info mmc dev 0 mmc part fatls mmc 0:1 ext4ls mmc0:2 mmc read 0x40000000 0 1 It seems like mega doesnt work anymore without login. Here are the images on gdrive: https://drive.google.com/drive/folders/1jEIWmzZgT5t39jRz7GwZpFOAdjdQBLtG?usp=drive_link

if you are not seeing option to enable in armbian-config you can try: sudo apt install xfce4 xfce4-terminal lightdm -y or sudo apt install xfce4-goodies -y

I experience the same problem: I installed Armbian without desktop (both the Debian and Ubuntu version) to install a minimalistic desktop setup afterwards. However, in the armbian-config tool I do not find the "Desktop" option when entering the "System" menu. The installation instructions mentioned in the documentation (Desktop Environments - Armbian Documentation) are not working either. I'm using Armbian 25.11.1 dzsnlr 6.12.58-current-bcm2711 (Debian trixie) on a Raspberry Pi 4 8Gb. Thanks a lot for any hints how to get a minimal desktop installed without relying on the images with desktop included!

Different attempt. Instead of working around trying to revert which might be the root cause: https://lists.openwall.net/linux-kernel/2025/09/17/618 I'll provide you with another image containing this adjustment shortly. https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.63_minimal.img.xz Could you do me a favour and execute these commands on both in a non-working state of a broken image and in working state of a good image? dmesg | grep -i "phy.*halt\|mdio.*reset" watch -n 1 'ethtool eth0 | grep -E "Speed|Duplex|Link detected"' cat /sys/class/net/eth0/phydev/phy_state 2>/dev/null Edit: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.63_minimal_regulator_fix.img.xz this image follows another different approach by adjusting regulators which may cause issues. Feel free to test

So to cut a long story short 6.18.y kernel image works? If so then this issue has low priority since 6.18 will replace 6.12 as current in a few month anyway since it is the new LTS kernel upstream.

i was installed armbian on hg680fj with schipset amlogic s905x2, replace dtb with spesific hg680fj and change xtlinux config, after that starting boot, but looping on armbian screen. please help ehat shoud i do.

Thank you. I'm gonna try that.

I haven't tested ufs yet. I think you have to add this extension in build/config/boards/radxa-cubie-a7a.csc enable_extension "ufs" https://github.com/NickAlilovic/build/blob/a733/config/boards/radxa-cubie-a7a.csc @chainsx is working on his own build. He just updated his build with a ufs fix. https://github.com/chainsx/build/tree/a733 You might need to add this to boot his images. Not sure if it's fix. NAME_INITRD="initrd.img-5.15.147-legacy-sun60iw2" or NAME_INITRD="initrd.img-6.6.98-vendor-sun60iw2"

I found a post on this forum and tried it, but it didn't appear to have any effect. I might have just run it wrong. I believe they were also dealing with a different source having this problem.

Here I leave my logs, if you need additional ones let me know: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether [MAC ADDRESS] brd ff:ff:ff:ff:ff:ff altname enx[XXXXX] 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether [MAC ADDRESS] brd ff:ff:ff:ff:ff:ff altname wlx[XXXXX] I tested the image provided and after numerous reboots it didn't work, still the same problem. Doing some other testing i compile the following image Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_forky_edge_6.18.2_minimal.img which I extracted it from Armbian GitHub from this tag: "v26.2.0-trunk.146" https://github.com/armbian/build/releases/tag/v26.2.0-trunk.146 and it worked. i don't know if it has to the with the kernel version or something but I think is something to consider.

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!