Igor

apt.armbian.com is published at point releases, from this branch https://github.com/armbian/build/tree/v24.05 If you check it out, you will get identical what is on stable repository. If you want to go manual way, here https://github.com/armbian/build/blob/v24.05/config/sources/git_sources.json are information about sources. beta.armbian.com is published every x hours from trunk https://github.com/armbian/build If you want to see how this is done, peek into this code. Kernel 6.8 and 6.1 are very very different. Don't expect 6.8 to work better or that all functions will work. Some are not even developed - it is being developed from scratch for around two years now. Code is changing fast, so there is not possible to provide any support. Its too expensive and useless. If you want dig in, but expect troubles and very little response as not many people deal with. 6.1 is different. All 3588 share same problems ... more or less and there is a lot of support in forums.

Can you provide a package or a file associated to this library? So we can find it and add.

There are some issues with Helios64 patches for 6.9.y https://github.com/armbian/build/pull/6691 Please check notes.

Not anymore ZFS, versions that we are adding is now again properly autotested: and this won't be happening in the future. If dependency check fails, packages are not pushed into the repo ...

This is certainly not deliberately and will probably be fixed soon. Open a bug and / or report here.

https://armbian.atlassian.net/browse/AR-2192 Fixed in latest release.

Change to "vendor" kernel 6.1.y is recommended.

I have (hopefully) fixes ZFS on all variants yesterday, but haven't tested on Debian yet. Works fine on Ubuntu based builds, ZFS v2.2.4. If you have time to test, beta.armbian.com should have proper packages: https://k-space.ee.armbian.com/beta/pool/bookworm-utils/z/zfs-linux/

Here you can make a donation. Thank you. That "Ubuntu" was in 99.99% developed by Armbian and other open source projects. Orangepi is HW dealer. They only care that hw features works. They never pushed fixes to common code. We have to spent our private time if we want to port / fix their HW bugs & features to better common code which is the only one maintained and which is in your interest to run it. Software you are so happy to use is on this level. We are maintaining software together and this issue was not closed. Do you really believe unmaintained promo software have only one problem? 😁 There is a new release out tomorrow. Every download page has daily assembled images with latest updates and fixes, where you should check if this problem was resolved. Did you check that before?

That is O.K., but Armbian build framework does not accept HW related tickets. Forum is right place where you can bring this up and discuss what to do. Then open a PR if solution emerges ... Without this patch, PCI probing will randomly fail. Which is worse then 100% going up in 1x. This is my 2c. I understand that you would like to have a perfect functioning PCI system on this hardware platform and if you cover someone several weeks of R&D, this can probably be done. Since this will not happen, we have partial solution/workaround in place, this forum and we have each other.

Or install attached with dpkg -i armbian*.deb armbian-config_24.5.0-trunk_all__1-SA8477-B2b14-R448a.deb

Perhaps this is a solution? https://github.com/armbian/build/pull/6652

Planned point release and images rebuild date is upcoming Saturday, 25th. There are three problems, that would be nice to fix before. People working on are very busy and might not be able to deal with, so help is needed here: Debian bookworm XFCE lacks wallpaper and lockscreen Compile from sources and pack Chromium for aarch64 on PPA Resolving Noble incompatibility with amazingfated-rk3588 extension Thank you all that participated in this release!

Two desktops needs additional testing: https://github.com/armbian/build/pull/6626 https://github.com/armbian/build/pull/6625 ... we are high on closing existing tasks and very low on time dealing with this. There are several other bugs that needs attention: https://www.armbian.com/participate/

Soon, in less then two weeks.

This forum is related to Armbian. For general Orangepi questions consider asking in their forums. We don't use Android nor Batocera here.

Testing ... 3588 vendor 6.1: Do we have a working? 3D hw support via panfork wiringpi support? npu? 4k youtube video playback under Chromium? 4k under MPV video player? https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml other rockchips. Enabling extensions? - v4l2loopback-dkms,mesa-oibaf What about amlogic, allwinnner? - v4l2loopback-dkms,mesa-oibaf Nice to have: rock-5-itx edge kernel Manually tested: - Bananapi M2PRO Gnome desktop with 4l2loopback-dkms and mesa-oibaf

I would not use ZFS with this kernel if I were you. This kernel is provided by hw vendor, by people / business that only cares about (selling) hardware features to work. Everything else is unmaintained and open source community (not just Armbian) developers are not even thinking to maintain this kernel outside that as its concorde fallacy. FYI - it is highly possible ZFS implementation is affected, but you are FREE to do whatever. 90% of solutions, not workarounds, Armbian team (a few people) is unable to integrate into OS with their private resources, public (thousands of you) are simply not there. I can estimate, we could integrate about 30% of resolved suggestions this community generate with few full time engineers. Which costs money. Until you are satisfied with reporting problems only, until you don't care that a lot of value is wasted, there is nothing we can do but keep trying to provide "best effort" support with what we have and explaining this situation. Users perspective will always be like we refuse to help ... but people that are working on / helping Armbian are already long maxed out in efforts of helping everyone, even our competitors. Also. Hardware vendors have exploit of open source community build into their business model. If it happens that you are using hardware with terrible vendors reputation, bugs can be written, but are last to be resolved, some bugs are never resolved ... If you really wanna help everyone, start here: https://github.com/armbian/os/wiki/Import-3rd-party-packages Study and implement a solution. We also have automated dependency testing, which should prevent this problem in first place, but ain't working well and it wouldn't help much in this case. ZFS package is imported from Trixie and yes I understand that upstream package dependency has been recently changed. Until a month ago, we didn't have this problem, everything was working right and now, there is little we can do except disabling importing (which will also delete packages from repository). We don't compile those packages on our own and I am aware that this is not the best way. There are more workarounds - like using Trixie or Noble user space ... Its sadly under-powered, too small. Math is simple - I would very much like to help, but costs are the one that are killing us. Imagine that fixing a problem costs 1000 USD. You are willing to pay 5 USD (or not even that), which is fair if there would be more people contributes their share that you cover all costs. This never happens. They come with another and another problem for 1000 USD (often a lot more, sometimes a lot less) instead. Then its expected that we pay the rest, 995 USD for costs of resolving community software problem, this is simply not sustainable way of cooperation. Even the bug was made by us. I am trying to keep ZFS available. Do you have any idea how much time loss this service already caused with no benefits whatsoever? There are thousands of bugs in open source software and most of people pin everything on us after they download "Armbian image" and images that are produced by copycats as they claim "its Armbian". This particular problem was introduced by us, yes, but alternatively would be not providing ZFS that is capable of working with recent kernels. Which touches to the core of embedded Linux experience and logic. Often we can't match user space and kernel like this is done on 1st class x86 desktop / server / hw Linux world. Even they, often breaks critical things too, even with thousands of full time employees (Redhat). We can't provide that level of services with close to nothing from your side.

Which SoCs and on which branch can have extensions enabled? 4l2loopback-dkms mesa-oibaf here: https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml#L40-L95 Mapping config: https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map

Oh, yes. This must also work. or "commit:xxxxxxxxxxxxxxxxx"

Hasn't changed. https://github.com/armbian/build/tree/main/patch/kernel Just symlinking of subfolder are perhaps adding some confusion.

Welcome! Remember that this is forum, not a professional technical support service that waits on problems. We are on the same side. Problems takes years to be resolved as there is nobody behind. They don't invest, you don't invest, we can't invest into support service you might with or expect. We didn't produce this hardware and manufacturer doesn't work with us. They almost literally throw hardware like bone to a dog. Armbian ultra small team have to deal with other things then this hardware / 3rd party (copy of) OS clients problems. Now you know. You came from a project that has bad reputation, you are using hardware from manufacturer that does not support open source software. They are not alone. More makers are abusing community to generate software, support and sales. But some genuine help and there our focus goes. Sometimes we made wrong judgements ... If you mentioned RPi. They are far from being modest example, but they are returning about 2M USD annually back to community. Here small dealers, who have no affection and understanding how non profit community works, are competing how well they will abuse this community. The more the more they will profit - that is why there is so much bad vibes here. Some are doing everything to optimise this abuse. Not talking just about Armbian, but developers community at large. No need to mention, that Dietpi is not a part of this game. They don't suffer as nobody never took anything from them in past 10 years. What did you expect? Truth or fake happiness and prompt resolving of your problem? With our private money and in private time? "Case number 125323". Perhaps weeks of research is needed. Not just trolling on forums? I believe you didn't know nothing about this and it feels me bad that I have to tell you this. But this is your problem too and I hope now you see why. If open source developers are not happy, you will not move them with anything. Just trying to draw you a bigger picture. Raspbian / RaspberryPi has IMO 20-30 full time engineers for supporting clients and they have classes easier job then we do. We have not a single one.

You might insult many people if you compare Armbian with Dietpi. They download Armbian (firmware is binary copy), run BASH script to re-brand, add their script junk and sell as "supported". When bug is found they say "oh, this trash Armbian", when someone say compliment, they take it. This is how piracy works in open source. Compliment and recognition of work is everything. They contribute nothing to Armbian, nor its possible to take anything. Where we would, as community, progress, if we would just steal and pretend? Board manufacturer is responsible to fix this problem. They know how and where change is needed. But ... they compete with OS we made with us. Are you sure, you are long enough around to see it all?

Actions: updating template for building standard support images. Keeping Jammy CLI and Jammy XFCE desktop, upgrade other Jammy to Noble. Keeping old stable user-land with more recent kernel is actually a perfect combination. download pages were adjusted to current status. branching to 24.5 freezing sources merging all board status changes making RC builds updating application builds lists updating 3rd party packages import regenerating repository with Ubuntu oracular switching nightly build targets to Ubuntu oracular generating RC images for application deployments returning armhf to Noble / Trixie RC0 RC1 (is in making) for testing: HomeAssistant, OpenHab, Security (Kali) https://github.com/armbian/distribution/releases/tag/24.5.RC0 Nightly images https://github.com/armbian/os/releases/tag/24.5.0-trunk.580 Stable builds (RC) https://k-space.ee.armbian.com/incoming/ https://fi.mirror.armbian.de/incoming/ Automated testings https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Report: - problems Suggest: - images that needs to be added, changed status @Contributor/Maintainer

apt install armbian-config