Igor

Yes, we even want to provide x86 Armbian ISO image + preinstalled all what is needed even our build script takes care about environment and install what is needed. TL;DR; Most of people, our CI, are cross compiling as its a lot faster due to lack of serious arm64 hardware.

Status on Jammy ZFS packages updates (and many others) is currently unknown as its maintainer is no longer with us, rip Jonathon.

Armbian components are kernel, boot loader, tweaks - those are all updated the same way, but Jammy has more recent user land packages as its assembled from Ubuntu packages (Canonical stuff should be cleaned out). I am using such assembly on all of my machines and its IMHO best combination. Regarding ZFS - we serve latest (2.1.6) from our repository (from), while with Debian, this applies to get latest.

With extensive hacking, in theory, perhaps, in reality? No. Same situation is with Lenovo X13s featuring the same SoC. You can boot Linaro hacked Debian with kernel 6.1.y / 6.2.y leaning on device tree.

I have removed htop from our repository. We are at least good for the future.

Check logs to understand why its not starting. Without CI, and interest that this is fixed from your side, we don't know that it breaks and why. I am trying to develop automated testings, but without help it will take years to complete. Ready-made Cinnamon images should work.

Fixed. Need review. https://github.com/armbian/build/pull/4710 Thanks @c0rnelius!

Event -> Video (with transcripts and comments) 1. Merging NEXT (Jira tickets) - many small fixes - windows build support (WSL2) - small machine support (smarter dependency handling) - better patch logging and logs in general - people contributing Focus on: - CI, aggregation, rootfs cache ( @Igor @rpardini) - testing, testing, testing (anyone) 2. Providing stable builds for main TV box image? We generally support this idea and builds can be enabled @SteeMan https://github.com/armbian/build/blob/master/config/targets.conf 3. None this week. Comments on all topics are welcome! @Contributor/Maintainer

Anyone reading this volunteer in helping us getting together some article we can ship to some a bit serious magazines. Equally useful if someone knows someone that this might be interesting topic to cover? Technical article about changes, improvements and benefits https://armbian.atlassian.net/browse/AR-1497

"I looked several days and find nothing - this is how software development looks like". Of i didn't, as in exchange for coffee, I simply can't afford that, nor nobody else can. I am running this place and this place helps you in any case and that is my 2c. That it helps you in best effort manner? That you find people sharing your problems? That we try to work on problems together? That you have opportunity to help? In case you want that driver is fixed, report it here https://bugzilla.kernel.org/ In open source software sometimes this takes months, sometimes years, sometimes its never resolved. If you want that it is fixed, hire someone to fix it for you. You need this fixed. If we would be able to, we would, but with coffee cash this is mission impossible. Auto login / random feature in images? Download a tool https://github.com/armbian/build, read documentation and do whatever you want. Remember we are drinking coffee 24/7 not just when you find a problem in software we didn't make, but we help you make it usable.

https://github.com/armbian/community/commit/2dc0a364c8a31e11d708885e0622f1be30402de1

How? This way?

Update has been initiated. 24 - 48h until it shows up in CDN.

You need to download sources, not headers.

I think we don't need armhf support.

We are running semi automated tests on real hardware (probably the only Linux distribution that do that) and it shows no problems with latest builds, similar to community: https://github.com/armbian/build/actions/workflows/smoke-tests.yml Try bad / another SD card. Armbian works.

We are unable to keep this complex install script updated. But I think official install script is now in pretty decent state: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ I haven't try but it looks like its well maintained.

Try this way: https://pivpn.io/

At least this part is relatively easy - generate a PR in similar fashion: https://github.com/armbian/build/pull/4611

Indeed. I would bet we have some undetected error in CI build process ... We are putting hopes to bring up armbian-next up as soon as possible as this will also give improved error detection and logging. In case you manage, welcome. Thank you for your input.

https://github.com/armbian/build/blob/master/CONTRIBUTING.md#generate-new-patch-template

6.1 is currently available only in beta / nightly repo. Switch there first, then you will be able to chose 6.1.y.

Event -> Video (with transcripts and comments) 1. Merging NEXT (Jira tickets / updated slides) We discussed progress and problems. Help is needed with: enabling CI developer perspective testing -> test all boot loader, old boot loaders, especially armhf images: cubox-i, odroids, clearfog, ... user perspective testing desktop (currently is broken?) 2. Encourage end-users to open bugs to Jira? Replacing https://www.armbian.com/bugs/ with instructions how to add a bug to Jira seems like a good idea. But this will be community managed without any obligation from Armbian team. Basically introducing a proper bug tracker. Existing AR-XXXX issues that are hardware specific should be moved there. If we have a consensus on that, we have to make a plan, write proper instructions and launch it ... or forget about. 3. Move developers forums to GitHub We were weighting idea to try to encourage more discussion on GitHub and have forum more users oriented. For start, we can try to enable Action - if label discussion is raised, it automatically creates a topic on GitHub discussions. Or similar. If we do that, we should first deal with hardware related bugs. For 2 and 3 we didn't come to any common conclusions except that communication is fragmented around forum, git, irc / discord, emails, PMs ... Comments on all topics are welcome! @Contributor/Maintainer

I am open for this idea - one of you needs to take responsibility to make it happen - I'll just run the build once is in the system. Can be discussed on regular developers meetings.