Igor

I would propose to build most recent ./compile EXPERT="yes" # to see EOS targets - that should give you latest latest, but since its unmaintained ... I have no idea if it works. Probably it does.
 

This box came with at least two different onboard wifi chips, which means you have to play with a device tree blob configuration to make it work. Drivers are most likely present in the kernel for all variants.
 

If you don't have support for DVFS, CPU runs at IIRC 50 or 60% of full speed ... which is why temps will stay low.
 

It depends who's asking  TV boxes are without schematics and without certainty that one model is identical to the same model, which means this job is more like a hacking ... 

If dkms package is already installed you need to run
 
dpkg-reconfigure zfs-dkms  
in order to force module recompilation. If missing ZFS modules is a problem.

Was unable to pull zfs-dkms 2.1.6 being available on cdn https://armbian.hosthatch.com/apt/pool/jammy-utils/z/zfs-linux/
After armbian-config and apt reconfigure mirrors and apt update && apt upgrade i could pull the zfs 2.1.6 goods (dkms and zfs-utils)
 
These values are and where fine
cat /etc/apt/sources.list
deb http://ports.ubuntu.com/ jammy main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ jammy main restricted universe multiverse
deb http://ports.ubuntu.com/ jammy-security main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ jammy-security main restricted universe multiverse
deb http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse
deb http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse
 
cat /etc/apt/sources.list.d/armbian.list
deb http://apt.armbian.com jammy main jammy-utils jammy-desktop
 
Not sure why apt reconfigure mirrors solved this.. but never the less, happy eyes with the zfs goods to play with.

Thanks!
 
If someone has time to integrate this to Armbian standard install tool:
 
https://github.com/armbian/build/blob/master/packages/bsp/common/usr/sbin/armbian-install
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-nvme-usb
 
+ packing sata spi bootloader within u-boot package (this part is a bit tricky as blob has to be provided and packed via custom UBOOT_TARGET_MAP)
https://github.com/armbian/build/blob/master/config/sources/families/rockchip-rk3588.conf

orangepi-5
orangepi3-lts
orange-pi-zero-2
orange-pi-zero
rock-5b
...

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

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

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

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

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

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

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

Building a git master "cli" image does seem to boot. E.g. with this commandline:
 
./compile.sh docker BOARD=rockpi-s BRANCH=edge RELEASE=jammy BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_ONLY=no KERNEL_CONFIGURE=no  
and armbian-build master 21186c0577c39699e04949366f094bda54960729, I built Armbian_23.02.0-trunk_Rockpi-s_jammy_edge_6.1.4.img which boots as expected.
 
Building 22.11.2 locally also shows the same problem (does not boot). E.g. with this commandline:
./compile.sh docker BOARD=rockpi-s BRANCH=edge RELEASE=jammy BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_ONLY=no KERNEL_CONFIGURE=no REPOSITORY_INSTALL=kernel,u-boot
./compile.sh docker BOARD=rockpi-s BRANCH=edge RELEASE=jammy BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_ONLY=no KERNEL_CONFIGURE=no REPOSITORY_INSTALL=kernel,u-boot and armbian-build v22.11 e323753fe7fb26f833dbfeab94351b38fe97550d, I built Armbian_22.11.2_Rockpi-s_jammy_edge_6.0.10.img which does not boot like the official builds.
Note that I used REPOSITORY_INSTALL here, since a locally-built kernel failed for some reason (net/bluetooth/hci_sync.c:3442:42: error: ‘HCI_QUIRK_BROKEN_PARK_LINK_STATUS’ undeclared.), which I have not further investigated.
 
Building git master with prebuilt kernel and u-boot does *not* boot:
./compile.sh docker BOARD=rockpi-s BRANCH=edge RELEASE=jammy BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_ONLY=no KERNEL_CONFIGURE=no REPOSITORY_INSTALL=kernel,u-boot and armbian-build master 21186c0577c39699e04949366f094bda54960729, I built Armbian_23.02.0-trunk_Rockpi-s_jammy_edge_6.0.10.img which fails to boot again.
 
Note that the kernel is actually different from the self-built master version, which got 6.1.4. This suggests that the problem is in the kernel, and 6.0.10 kernel is broken and 6.1.4 fixed it, except that the problem also occurred with 5.19.16 jammy, but that same kernel worked with bullseye (so at least there is more than just the kernel involved).
 
Doing the same built with just REPOSITORY_INSTALL=kernel (so rebuilding u-boot) also fails, removing REPOSITORY_INSTALL entirely again (so the same built as the first one in this post), things boot again, confirming that the difference is not in something that has been cached along the way.
 
 
Conclusion: Likely the problem has been fixed in git master. I'll retest the official images once 23.02 is released (if I remember...).

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 was able to boot Armbian on Radxa Zero only with built-in flash memory (2 and 4 GB versions). 1 GB and 512 MB versions constantly reload on boot. I tried several SD cards (SanDisk, Adata, Samsung and noname), cards running on 2 and 4 GB versions do not run on 0.512 and 1 GB boards. I have on hand 512 MB, 2 and 4 GB versions of the boards. How can I help?
https://armbian.atlassian.net/browse/AR-1148

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.

I'm an id10t.  call in the St Bernards and drink the whisky yourselves.  It was the .config file it uses to make flash. Its not a pure text file. Blowing it away and doing a fresh make menuconfig fixed it
 
.

Thank you! 
 
Impossible without help of:
@Contributor/Maintainer 
@Moderators
https://github.com/orgs/armbian/people 
https://github.com/armbian/build/graphs/contributors 
https://docs.armbian.com/Release_Board-Maintainers/
...

Some people had troubles, indeed. Images were replaced today and they have been tested. Try. (download might be slow / not synced to all servers yet / use torrent or retry if you are going to try within next couple of hours)

Thank you! 
 
Impossible without help of:
@Contributor/Maintainer 
@Moderators
https://github.com/orgs/armbian/people 
https://github.com/armbian/build/graphs/contributors 
https://docs.armbian.com/Release_Board-Maintainers/
...

You mean adjusting HW features? Because there are no overlays and nobody developed them. No, we have not plans nor budget for that.
 

We are also waiting and waiting that you realise that you need to support R&D in order to have some small rights to complain  
 
This graph below shows how many days is needed before reported issues is resolved. Terrible, right? https://docs.armbian.com/User-Guide_FAQ/#development-time Remember that if you don't contribute on the project, you can't add bugs / tasks to the system at all. With another words - we have no resources not even for write bugs into the system and if we would listen to your problems, situation for the project that helps you, but you don't help it, would only be much worse.

 
If all people that complain and report bugs to themselves would have Angel https://forum.armbian.com/subscriptions/ we would be able to perhaps hire full time person for you that would record bugs and solve them one by one. Since this is not the case and you expect the impossible, graph can only get steeper. 

a bit late but the problem was I forgot to add the line "[Seat:*]"

Bulk is recommended 😎
 

 

Event -> Video (with transcripts and comments)
 
1. Checking the progress of Armbian-next. 
 
most of open bugs has been fixed.  
How to help?
 
users? continue to test various variants -> open a ticket developers? focus on cleaning rockchip64 / media patches, focus into config/ section -> moving family and board hacks into extensions  
2. Armbian short description
 
We are still not unified. Most sane idea is to better divide Armbian as OS for end users and Armbian as a build system for developers / integrator / business users and name those two more appropriate. We couldn't unite on a name to fit it all. 
 
3. Mainlining of patches
 
We generally agree and encourage this but we can deal with this gradually. Cleaning and squashing patches first, then move on. While doing this perhaps mark what could be good candidate to mainline so we don't press on people to proceed right on the spot.

I understand. I cannot apply 😆 but will act accordingly. thx