Igor

You can try to make an image from stock u-boot and kernel if you like. Just proceed this way: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ but it is unknown how much of work that represent. I can be an easy job, but can also take weeks to months.

Those are developers preview builds, where you can check what works and at some point it will be good enough for some uses cases. In a couple of years, it will be functional on the level of kernel 5.10.y. Download is possible from CI pipeline: https://github.com/armbian/build/releases Boot log: This board is looking for maintainer(s) and (this) forum moderator (contact @Werner).

Wireguard does not build as its already present in the kernel and that DKMS package is needed (is build-able) only for kernels older then 5.5.y. I have recently re-imaged my HC4 NAS and everything works perfectly OOB: ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 System load: 2% Up time: 13 days 21:42 Memory usage: 58% of 3.70G IP: 10.0.60.7 CPU temp: 49°C Usage of /: 12% of 15G RX today: 1.2 GiB ZFS pool: Online odroidhc4:~:# modinfo wireguard filename: /lib/modules/5.19.17-meson64/kernel/drivers/net/wireguard/wireguard.ko.xz alias: net-pf-16-proto-16-family-wireguard alias: rtnl-link-wireguard Ofc you can go several steps back and assemble image from raw Debian and generic ARM Linux kernel. But you will probably certainly run into more troubles.

You can. But until this is resolved, it works (well) only in Ubuntu userland as we build with Ubuntu compilers.

RC builds are also ready - need someone to confirm builds are o.k.

It doesn't pull DTB package ... [ .... ] Installing from repository [ linux-u-boot-station-m3-legacy ] [ .... ] Installing from repository [ linux-image-legacy-station-m3 ] [ .... ] Installing from repository [ armbian-bsp-cli-station-m3 ] [ .... ] Installing from repository [ armbian-firmware ] [ .... ] Installing from repository [ armbian-config ] [ .... ] Installing from repository [ armbian-zsh ]

They are generating images from packages that are in repository. But since packages are there, I don't understand why they are not included in the image. In case of network error, build should fail. This way has to generate working image: ./compile.sh EXPERT=yes NO_APT_CACHER="yes" BETA="yes" is the closest to automated build - followed by selecting "use packages from repository".

You mean this? There is DT package - if it was not assembled, perhaps there is another problem? https://imola.armbian.com/beta/pool/main/l/linux-5.10.66-station-m3/ Please start merging this into Rochip64 as I don't follow anymore - media kernel, integrated dt, extlinux, efi ...

Images were made before your fix and they won't be recreated until next batch, perhaps in a week.

This is our test device: Full logs: https://paste.armbian.com/qeqisakege (sudo armbianmonitor -u) How do you power this board?

I have seen some problems reporting on Rock64 / RK3328 (boots but desktop doesn't load) and Orangepi 4 (old one) not boot at all. If someone can check on this or similar devices. I can fastest tomorrow evening.

OK, no worries. Just our MO starts from the hardware perspective first. Armbian team can't really help as this is most likely an software provider issue and if you don't use official Innovato build, sound might not work ... that's why we are jumping up But like you said, someone might install it ... this is forum, so perhaps someone did and will tell something about. 73 de Igor

Thank you! Many people here are speaking this 1,2,3,4,5 language Most helpful to Armbian is help on maintaining our core build system and second hardware that we are stuffed with ... I have sent you an welcome to the email associated with this account.

Safest way is to download XFCE image and proceed as stated in the image I have pasted. It is at most important you follow instructions as stated, generate username. If this doesn't work and if also RC candidate images are not working, then we might have some problem. It can be a small one or weeks of work ... I always note that vendor never supported what we are doing for you. And you ofc expects that this just works.

This way must work and this is what we are testing. Sometimes graphical drivers or some library breaks down (unrelated to our work) and things breaks down. It happened before and it will certainly happen in the future. This is Linux and cheaper hardware its hard to find ... For manual way - installing from CLI - you have to know what you are doing. This is not Armbian problem anymore.

Did you proceed this way:?

Anyway an application issue as I would assume sound works on Innovato Armbian builds.

If your sound works in the system (from here on its not an OS problem anymore) but not in this application, than you have to search application developer instructions, file a bug to them (Wsytx). If sound doesn't work anywhere but you are using official Armbian on the officially supported hardware, then this way.

Known problem, yes. We are working on solving it for some time, but don't know how far we got. @rpardini Are we addressing this problem in the armbian-next somehow? Basically we need to compile kernel + headers per distribution/gcc which means 4 x more kernels to build, pack and distribute. From around 40 to 160 kernels + headers packages. This will be a bit of a problem as we only have around 1000 CPU cores for CI compilation ... which is already on the edge.

Send fix to master as we won't move any further. I will merge it to v22.11 right before rebuild.

If you check your /etc/apt/sources.list you can see that deb-src repository is not enabled by default. Enable it. Basically just follow instructions on this Debian wiki. We are not changing userland packages - we use Debian packages assembled in our way + additional packages. We don't build vim, but ship Debian package ... Only the critical things are ours: kernel, u-boot, hardware support package, tools for handling hardware, ZSH package, firmware, ... If you want to change ours, except kernel, you need to use build tools as those are n/a in a standard deb-src form.

Make a PR here https://docs.armbian.com/Release_Board-Maintainers/ so we have an actual picture. Yes ofc. It is important we start with testings. As we spoke, I am fine with postponing release date in order to not compromise quality of release too much.

Nope, but 8cx has some chances as there is some initial development going on, but someone has to donate at least one test device and cover hours wasting playing with it.

RC images are uploading to https://imola.armbian.com/dl/BOARDNAME/rc (patience, download will be slow!) If you find a bug, just open a Jira / PR only in case of small typo thing as such https://github.com/armbian/build/pull/4456 https://www.armbian.com/rc-testing/ Tested manually: Olimex A64 Bullseye CLI current, installed ZFS, installed to eMMC, reboot Orangepi 3LTS, Jammy CLI, current, installed ZFS, installed to eMMC, reboot

https://github.com/armbian/build/pull/4399