I've finally managed to boot from btrfs in uboot 2024.01. The problem was not a new bug (there was only a few small btrfs related changes since previously used uboot 2022.10), but some old limitations/bugs uncovered by uboot's switch from distroboot to bootflow. One bug has already been fixed in 2024.04 and another (out of bounds write) is not fixed yet. I have sent PR to armbian and will try to push it uboot upstream (ohhh, good ol maillists)

I would love to. I just want to get it working in any regard, as at the moment it serves as nothing but a very expensive drink coaster.. haha Apparently this board has the option to boot from SD card, and I have attempted to boot both Linux and Android variants (for this chipset, but not specific device) from the card without any luck.. I feel that maybe the device isn't defaulting to the boot from SD option though, as it is still seeing some type of software back-end. Do you happen to have any suggestions? Unfortunately at the moment I do not have access to an oscilloscope, but I will try to get a hold of one later in the week I have absolutely no idea how to do this, but I'm more than willing to try (and will certainly share it) I appreciate your response and guidance thanks @Hqnicolas

I ran an update on my orangpi PC2. Setting up armbian-zsh (24.5.1) ... cp: cannot create directory '/home/unifi/.oh-my-zsh': No such file or directory cp: cannot create regular file '/home/unifi/.zshrc': No such file or directory chown: cannot access '/home/unifi/.oh-my-zsh': No such file or directory chown: cannot access '/home/unifi/.zshrc': No such file or directory Witch is to be expected to fail, because that is a system user I accedentally gave an above 1000 UID Unifi is UID 1003, my regular user bedna (1000) is the owner of /home/bedna I don't mind, I don't use zsh anyway, but figured you would want to know about this. Edit I spoke to early, the update actually breaks the system. Seems to be network related because it gets stuck at that if I connect a display to the device. I have restored a backup and retried 2 times, same thing, so there is presumably something wrong on your side here. This is what the terminal gave during the update, and as you can see, it looks like it all goes smooth, something in the firmware or kernel?

I think @Niel Mar Bagay was searching for Ophub

It seems like things have evolved in the Middle East. Do you intend to make space available to the opensource community there?