Igor

HDMI could have troubles. Did you try serial console?

I have noticed ... I assume there is nothing wrong with overlay? Why would we remove it? Recording a bug into Jira is all what we can do. Unless someone has so much time to dig in and understand why it broke down.

https://github.com/armbian/build/commit/a712d7aebc39f16484b9eb787b23b445e6c76732 7th version of rockchip kernel ? config/templates/config-docker.conf is not merged well lib/functions/compilation/patch/kernel-drivers.sh (behind / merged wrong , we have GITHUB as variable not hardcoded for those sources) It is difficult to review functions that were split into new files, but I would propose to: - fix known bugs, resolve wireless / kernel-drivers hast to work (not optimal also fine) ... then open a merge request so we can start reviewing properly.

@rpardini I am still blocked Can't use bundles from git.kernel.org ... USE_MAINLINE_GOOGLE_MIRROR="yes", what about other mirrors? we should exit if HOST is less them Jammy, since Git is too old. Clearfog (current) fails at compiling u-boot (we can't go up with u-boot, too much work) Cubox fails at compiling u-boot (we can't go up with u-boot, too much work) Helios, kernel breaks when using Google mirror with: I'll also try to dig into the code if I can find something ...

If CI does the job, none. We update kernels in beta pool when sources are changed.

Desktop is hardware agnostic - it is the same on all HW so its best to develop and test on fastest and most reliable device you have around. I use KVM virtualisation on my x86 desktop, which is fast and has plenty of memory. I assume you have some PC (For Mac M1 use arm64) to use it for that? Download x86 Armbian image https://imola.armbian.com/dl/uefi-x86/archive/ and run it in virtual environment. You can find people that tackle desktop in #armbian-desktop at https://docs.armbian.com/Community_IRC/#channels We need to test desktops, their deployments, functioning, if they can be installed on top of CLI ...

Images were tested on PHYTIUM D2000 but if they work on newer / other versions, Armbian can only say "probably". If there will be problems, you have to deal with manufacturer to fix or pay someone to fix possible bugs for you. Then send a patch (or upstream) and our images will work (better). We provide and maintain build framework, sources are available.

Understand. I will do my best to lower the impact of those change to everyone involved. We are all involved in many things and our work is important for other people too. We don't want to generate them pain by providing tool that is crippled / unmatured. I agree. We have to improve our caching systems. No other way. Neither I, but together we will win

If you mean build-all way, then this is deprecated. CI now generate all packages from the outside. If its possible, for example, generate BSP package or U-boot package only and skip generating the rest, job is done. This is rarely used but we should have this (or some other way) to generate packages from sources. Within chroot ... Would be sane to place bundles to our servers and how much space / resources we would need for that? my 2c

We were blocked twice by kernel.org (still blocked) because our CI is generating too much requests. We need to establish https://kernel.org/best-way-to-do-linux-clones-for-your-ci.html and this mechanism is moving into this direction. Current mechanism is also broken. When using Google mirrors: [ o.k. ] Checking git sources [ linux-mainline/5.17 https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stableorigin/linux-5.17.y ] [ o.k. ] Add original git sources [ linux-mainline/5.17 origin/linux-5.17.y ] fatal: Server does not support --shallow-exclude fatal: the remote end hung up unexpectedly fatal: Server does not support --shallow-exclude fatal: the remote end hung up unexpectedly fatal: Server does not support --deepen fatal: the remote end hung up unexpectedly fatal: Server does not support --deepen fatal: the remote end hung up unexpectedly Nothing new to pack. remote: Sending approximately 2.59 GiB ... I am sure there are bugs but it also solves many problems we have in the current script. We are not merging at all costs, but we have to try.

Its impossible to get all people together and this meeting was anyway on a short notice due to upcoming holidays and the fact we are late. Anytime, at once - found something?, file a bug. Focus is CURRENT kernel, others are optional. Check once again in Jira if closed and on device, after code freeze. That would be ideal process for now. I hope we are going to bump automated testings on a better level soon, so not much manual intervention will be needed. Other general things like bug in 1st run script or similar, should also be booked to Jira. Unless they are not already present. In case something else, not something from your field needs to be closed or moved ahead (to this version), help is welcome. Somebody has to do it ...

I think problems started this way. Each time we generate caches, already generated ones are checked for integrity and if that fails for some reason, cache is deleted and its made again but if one program in this package is updated or if there is any other change in the rootfs, which usually is, torrent and its hash is different with the same filename. File on primary server is changed, but not (yet) all others. When you start downloading, you always get latest torrent files which has (had) weblinks. URL to files, which have the same hash but are not the same. This is not treated properly as corruption and download never finishes ... A better hash re-generation mechanism, that would render out this corner case, and we could enable this back. But since we are already full of work and this is not that critical problem I choose to just disable web links ...

Release Candidate Code Freeze Date: 2022-05-14 Release Planning Meeting Date: 2022-04-23 14:00 UTC+1 Release Planning Meeting Location: Armbian IRC Release Date: 2022-05-28 Release Coordinator: Igor Board maintainers: @Contributor/Maintainer Open / close bugs related to your board in Jira for your board and close them if they are resolved before release date. Record also bugs that were closed but they were not recorded to Jira (to have this info in release documentation) Bugs that are resolved change field "Fix versions" to "22.05". Optional select board and SOC. Everyone with Jira access: @private/contributor claim ownership of closed tasks (Assignee) close issues if they are done (change field "Fix versions" to "22.05") move issues to next release cycle (this needs to be done) or backlog (one day) Anyone that wants to join: we are fairly good in maintain hardware, a little less in tweaking OS and desktops, ... We are good with infrastructure, except forums. Here we need help in moderating and reorganising. We also need help in leading projects. Like this release cycle and many small projects. If you wanna join coordinating release, read this ... Meeting preface:

Its a bug in Torrent protocol when using web seeds which dramatically speeds up download. I have removed them. Restart service in about 1h that your torrent files will be refreshed. Perhaps you will need to manually remove them all before (without removing files). Some files will be downloaded again ... that is normal.

Only option for some time according to @Neil Armstrong

Samples arrived ♥️ HW looks fascinating, Armbian is yet to be ported so can't comment how good this is in realworld. Its shipped with stock Khadas Ubuntu, kernel 5.4.y, which is good to boot something ... Technical specs at CNX.

First official nightly builds https://imola.armbian.com/dl/orangepi3-lts/nightly/

More pull request review needed https://github.com/armbian/build/pulls

When we will be able to cover costs of that operation. When there will be fair compensation for bug fixing and maintaining that service. One bug can easily eat a week, two, some months of a full time person. Since there is negative cash flow, that can't happen. We are not in a position to fund better support service that will have better exploit ratio. Just crazy, right? Armbian is nothing alike Raspberry Pi foundation with support budget millions of euros. Or RedHat. Where you pay first, ask questions next. I also sometimes remind people that serious costs are needed to be considered if they want something to be fixed, but usually this leads nowhere. If fixing has to be done, weeks of works remain on us ... also in behalf of our competitors and Linux community at large. Armbian comes with best effort community support - which is this forum. https://www.armbian.com/newsflash/armbian-needs-your-help/ https://www.armbian.com/newsflash/armbian-22-02-pig-release-announcement/https://forum.armbian.com/subscriptions/

Currently your donations only covers electricity for building images so you are very far away. I am sure donate button is easy to find and when donation(s) comes on the levels that we will be able to hire people that will support you, then we will proceed. Until then, we are forced to drop support in order to maintain sanity and contact with our families.

Kernel 5.15.y comes with EDGE kernel branch. In theory it should be able to switch within armbian-config but some features might not work ... Download and make a separate image and try before.

___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.02.1 Jammy with bleeding edge Linux 5.15.30-meson64 No end-user support: unsupported (jammy) userspace! System load: 102% Up time: 1:42 Memory usage: 69% of 3.70G Zram usage: 8% of 1.85G IP: 10.0.10.7 CPU temp: 66°C Usage of /: 3% of 58G ZFS pool: Online I am running Armbian Jammy with ZFS 2.1.2 odroidhc4:~:% zpool status pool: tank state: ONLINE config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ata-WDC_WD80EFAX-68KNBN0_VDJKU00K ONLINE 0 0 0 cache ata-SAMSUNG_MZ7PD256HAFV-000H7_S16PNYAD800646 ONLINE 0 0 0 errors: No known data errors Just to add that this is achieved in straightforward manner: 1. Download CLI image from download pages 2. Install headers via armbian-config 3. Installing packages: zfs-dkms zfsutils-linux Done. Then dealing with ZFS.

Special purpose driven hardware is not amateur distro hopper friendly. This might help to understand. This is forum and not a technical support service. Moderators will move it to correct place. Double posting is an offence / disrespect on forums. Please try to understand the difference - making friends and your contribution is essential. Professional support service is very far away. R&D even further. If you need that everything works perfectly, you need to hire someone and share your investment into FOSS with everyone. This is a support contract you have with Armbian, where it doesn't say anything about sponsoring bug fixing users find. Support is done in "best effort" manner and "no effort" if you are using a product based on Armbian. IMO if you want to use this hardware, stick to Armbian with 5.10.y kernel. If you want that device follow kernel development, sponsor weeks of full-time engineer time and contribute to this community and project best way you can. https://forum.armbian.com/staffapplications/ https://www.armbian.com/donate/ Help people which are responsible that you don't need to throw this device into the trash. Cover for - what works - first. FA knows what they are doing. HW is well designed, within reference design, don't worry about that. SoC has one internal phy and the other is attached either to usb or pci bus. P.S. The reason why you were unable to reply at once after registering is a spam prevention and fighting against forum transforming into technical support service. Where "customer" is a king. Once again. This is forum - perhaps contributing first? Asking for services worth tens of thousands of euros can wait. Weeks - years. New users also tend to ask too many questions in a very short period of time - like "i found out this is not working for me", while most of those problems are known, just there are no resources to address them. Users should also be using knowledge and information search function first to save precious resources which might be able to help them some day. Then they should search forum if topic they are interested in is not already open ... Anyway, welcome!

Indeed, my second NAS is cooling again Information added to https://www.armbian.com/odroid-hc4/ @Technicavolous There has been some recent fixes close to this topic. Dunno if they cover this.