Igor

Carefully transfer TV boxes back to the main index and remove the rest? Yeah, why not. @SteeMan@jock What do you think?

Also what we have is assembled here https://github.com/armbian/stationery Also worth mention - changes on download pages - example of download page with a full selection of CLI and desktops https://www.armbian.com/uefi-x86/ (expanded a few days ago).

Initial design was a mixture of https://www.primaprodukcija.si/ (they focused in UX and website back-end software) forum theme (Haze, which no longer exists) and our tweaks. In fact we took colours from forum theme and apply them to the website. I am not from design world ... i think only those base colours were defined, red, this "almost black" and light blue for links & buttons used on web page.

Try with: sudo apt install xfce4-power-manager @littlecxm https://github.com/armbian/build/blob/master/config/boards/pinebook-pro.conf#L8

Worth comparing if not already: https://github.com/armbian/build/blob/master/config/sources/families/include/rockchip64_common.inc

Thanks! I have temporally disable those that are not in sync yet.

Images were rebuilt and tested for corruption twice. None found. Download might be slow since syncing is still in progress.

Build done, none of the images is corrupted this time. The only change in runners setup is removal of dual 10Gb connection (Intel X710-AT2 in LACP bundle), which connection was unstable. Population to servers in progress for next couple of hours.

Rpi overlays were not bring there yet. Manual overlay as on stock OS: https://bootlin.com/blog/enabling-new-hardware-on-raspberry-pi-with-device-tree-overlays/

No. You don't need to do anything. We are in control https://github.com/armbian/dl-router (newer version of this is currently in operations)

This mirror is out of sync and was disabled temporally.

@Contributor/Maintainer Updates on legacy / current kernels (where only a patch version is changed) and u-boot packages (many from Rockchip family are broken on current release / update is anyway optional) are going to repository today, images repack follows. Huge task ...

There are several ways, this is one of the fastest: https://docs.armbian.com/Developer-Guide_Build-Preparation/#building-armbian

Build image from sources. It has different boot loader.

Its hard to miss, but this is what project needs: https://forum.armbian.com/staffapplications/ https://forum.armbian.com/subscriptions/ https://www.armbian.com/donate Maintainers needs to eat and pay their bills. There are several people full time just to maintain this project in general. Will the purchase to support ali-express business and you support their time? Rather donate money to charity. We can easily get HW for free. This is how entirely support is build up - throw some HW to community and they will support it for free. But there are very little people that knows and can afford to spent endless hours making endless variants of HW operational. We can also purchase it easily since this is close to nothing expense versus expenses we have by dealing with this project. Number are out of date, but it gives you the frame. For that you need to register / become a maintainer. Then someone (you or your hw vendor don't support) will call you to assist, when and if that is required. Bugs will be found but anyway we don't have ability (resources) to record or fix bugs since operation is too expensive. But its a path, we can hire people for you, if you need this. We don't. HW they design, throw out, focus on sales, in the same time they already design a new board ... Software needs constant support while you expect it for free, HW sellers give nothing on that. And also can't do much neither. Selling poorly designed hardware with promise of software reliability but in fact with no/poor software support leaving expenses of R&D and maintaining to the community?

Lets do some quick reality check. - dietpi uses our kernel without any changes. They only do branding / bash scripting / software installer. When something breaks down, they come to this forum as you did. - manjaro builds what comes to mainline which can only be worse then our untested automated builds from the trunk https://github.com/armbian/build/releases/tag/latest None of those provides any support you have in mind - bug fixes are not coming from those directions - and others are not even close to this. Fixing is more like random chaos. If you wants that things improve, you can support our project by understanding what we actually do, by making a donation / subscription so we will be some day able to hire people to support random hardware you are purchasing without software support from Ali-express. We are long over maximum capacity and bug resolution span is around one year. ... because of lack of support from users / vendor / * side. And you are putting a pressure on Armbian? Crazy.

Added a script so we can check them in 10m with a click on a button. (after release is made) https://github.com/armbian/build/pull/3915 The only fast (few days of work since it never goes as planned) repair is - recompiling all images, running this test and if not o.k. do it again ... and identifying why this happens, fix trouble, adjust code, do it again and again until things are o.k. This is how complex systems operations looks like. When all those little things will have unit testings attached too, problems will be detected earlier ...

@Contributor/Maintainer Certain issues has been reported, we know some images are corrupted due to CI issues. Planned package changes for (v22.05.2) will be BSP, U-boot, but we can probably also update all kernels if we are confident enough and if smoke tests will go trough? DUE in about a week.

It always helps to see full logs to understand. Even that doesn't tell everything, but helps. Here are mine: http://ix.io/3ZDX I have update mine and it went well. Even ZFS modules has successfully recompiled upon kernel change: ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.02.1 Jammy with bleeding edge Linux 5.15.30-meson64 No end-user support: unsupported (jammy) userspace! System load: 2% Up time: 7 days 8:49 Memory usage: 11% of 3.70G IP: CPU temp: 47°C Usage of /: 3% of 58G ZFS pool: Online [ 19 security updates available, 134 updates total: apt upgrade ] Last check: 2022-06-07 00:00 Last login: Tue May 31 15:24:08 2022 from 10.0.10.2 ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.05.1 Jammy with bleeding edge Linux 5.17.13-meson64 System load: 42% Up time: 0 min Memory usage: 13% of 3.70G IP: CPU temp: 52°C Usage of /: 3% of 58G ZFS pool: Online Boot stability on Amlogic boards has been a long standing battle and I am not sure its over ...

Assembly is software and software breaks down. I will not even record this problem since there are no resources. OP can build from sources.

Agree. This section needs changes. We are finally moving with https://github.com/armbian/configurator (not yet in human understandable format, but welcome to join inspecting the code) and once we get to the network config section, this should be adjusted. I think we should simply remove ifupdown and provide netplan, which can be use either for Network manager or systemd-networkd.

3 dedicated servers are fully updated by now, but one was down due crash - lack of memory. No idea what we can do to improve seeding rate. Adding web links would solve this, but opens other problem.

Problem is on our side and a bug has been opened to the infrastructure team. You can switch to https://redirect.armbian.com/torrent/all-torrents.zip (permanent) or wait that is fixed.

All you need to do is to test if patch provided by @Skupsy is working and integrate it: https://docs.armbian.com/Process_Contribute/ If this is a solution say thanks to him and to us for keeping build framework system in good health and for the guidance. And check your support contract.

I think you need to read FAQ and once you are done with updating and testing, make an integration request. Which is already a burden to the project but that you can cover with a donation.