Werner

Simply doing git clone on the repository and then using "git checkout v22.05" should do the trick. With git branch you can then check on which branch you are.

orangepi-r1 - no issues observed.

Tested:
Armbian_22.05.1_Orangepi-r1plus-lts_bullseye_current_5.15.35
Armbian_22.05.1_Orangepi-r1_focal_current_5.15.35
Armbian_22.05.1_Orangepi-r1_jammy_edge_5.17.5

iperf on wifi and both Ethernet interfaces produced expected results.

orangepizeroplus - no issues observed.

Tested:
Armbian_22.05.1_Orangepizeroplus_bullseye_current_5.15.35
Armbian_22.05.1_Orangepizeroplus_focal_current_5.15.35
Armbian_22.05.1_Orangepizeroplus_jammy_edge_5.17.5
 
iperf on wifi and Ethernet interfaces produced expected results.

22.05.1_espressobin_bullseye_current_5.15.35.img.xz - no issues on ebin v5
22.05.1_espressobin_jammy_edge_5.17.5.img.xz - no issues on ebin v5

I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...

Since we now have a dedicated place for this board (and basically every supported board) I'd strongly suggest to close this (and other) mega-thread and create individual threads per problem/question to increase user experience and readability. @balbes150

@Contributor/Maintainer

"missed released will result in immediate forfeit of “Armbian Supported” status and demotion to CSC status unless Armbian team grants exemption
https://docs.armbian.com/User-Guide_Board-Support-Rules/
 
Probably board maintainers are not aware, status will be dropped to CSC in case they don't show up. 
@yang Can you send them a notice to help with testing? One RC images are out and new RC will go out probably this weekend.

Sorry could not make the meeting.  I just read the notes.
 
I am back to work now but locally (almost no travel) so I can have a little time here and there maybe to help with the release somehow.
 
I'll try to hang out in IRC.

Was kind a painful to add 70 tags by hand one by one since invision refuses to deal with either spaces, tabs or line-breaks...
anyway all supported boards got their individual tag. in bug tracker forums only those must be chosen, for some other forums tags are open but supported board tags are marked as recommended.

Providing logs with 
armbianmonitor -u  helps with troubleshooting and significantly raises chances that issue gets addressed.
 
Also armbian-config did not receive much love within the last few month for once lack of resources and also as it is under major rewrite.
Basically what it does is to run a couple of commands and adjust a few config files which all can be done by hand as well. Just check the source code here: https://github.com/armbian/config/blob/master/debian-config-jobs
 
 

No idea. Maybe @Igor can or cannot confirm a fix since he is maintainer for OPi4.

Userspace upgrades (Buster->Bullseye or Focal->Jammy) are neither tested nor supported.
 
Try replacing rootfs package.

I tested with 4 archived images today.
GOOD is enp1s0 works fine with warm reboot.
BAD is enp1s0 works only after cold boot.
 
Armbian_20.11.10_Nanopi-r4s_focal_current_5.9.14.img.xz :GOOD
Armbian_21.08.1_Nanopi-r4s_bullseye_current_5.10.60.img.xz :GOOD
Armbian_21.08.1_Nanopi-r4s_hirsute_edge_5.13.12.img.xz :BAD
Armbian_22.02.1_Nanopi-r4s_jammy_edge_5.16.11.img.xz :BAD
and current my system is Armbian 22.02.1 with bullseye 5.15.25 :BAD
 
So I think,
Armbian version does not matter.
Debian (or ubuntu) version does not matter, either.
Kernel version (5.13 and above) may cause something.
 
Now I downgraded my system's kernel to 5.10.63 with via armbian-config.
And enp1s0 normally works after warm reboot again.
 
If you need more information that I can provide for this issue, please let me know.
Thank you.

As you may have probably noticed we have shifted a few forums around.
I know it looks a bit incomplete and inconsistent for now but we are unfortunately stuck due to a bug in 3rd party software and need to wait for fixing until we can continue.
 
Stay tuned

There is a similar topic. Check here:
 

@private/contributor 
 
Unifying TAGS as much as possible - as low count / universal as possible has been enforced to GitHub merge requests and issues. From now on, we have only 12 labels:


 

Then yours probably is not named with a color but with purpose. Simply try adjusting all of them and see what happens. You cannot do any harm doing so.
My best guess would be the user-led ...

Release is not just freezing the code and generating images. Its a time when we pull together stronger, agree and deal with common goals and ideas. Things we are dealing with are complicated. Linux is complex, our framework is getting there too and only together we can deal with all this.
 
I started on freezing the kernel version. There is also some breakage, some related to our patches, some not. But since we have to freeze it sooner or later, perhaps now its the right time.
 
This brings a few good things at once:
temporally release people that are working close with maintaining kernel code @going@jock@balbes150@amazingfate myself ... this can bring more resources on trying to match with / merge armbian-next. @rpardiniworked for moths on this. Lets review the code and help sorting out bugs. Again. IMHO it is possible to merge, but if code remain unstable by the code freeze date (2022-05-14), we are merging after new images are generated. asking @Contributor/Maintainer board maintainers to engage in images building and testing (currently still from master branch) and bug reporting as earlier as possible (once PR 3736 gets merged) reproducible build framework in release branch. Which is most important long term consequence. Additionally, we would like to finish u-boot upgrade on Rockchip and release major forum refactoring @TonyMac32 @piter75 @balbes150
 
Happy Workers' Day!

Or I guess Balbes support is free and easy.    
 
Note this is balbes and not official support status

I assume Balbes will mention if BT is functional in other kernels than legacy...
 

Thank you Werner and Igor,
 
Your valuable commitments and all you've done here is very commendable indeed!
 
Kind words, and grateful for the advice.
 
Best,
Alistair

Only general development on rockchip64 family. However since Helios64 has no maintainer changes there could also break functionality.

Try to install manually to get an idea about what is wrong.
The armbian-config tool basically does this when selecting tvheadend for installation:
 
https://github.com/armbian/config/blob/c9a9b494c3069807471bb00c0336566cd186f6d9/debian-software#L615-L635

Should, yes, but doesn't. RK3399 has an internal fixed boot priority which is something like SPI - eMMC - microSD - NVMe. This cannot be altered.
Armbian works around this by installing a boot loader to eMMC which points back to microSD and if that fails continue to boot from whatever is available instead.
If there is a boot loader on the eMMC that does not do that you have a hard time. That is why pbp installed an internal switch to disconnect eMMC from power to allow microSD to boot.

Both.
https://docs.armbian.com/#what-is-armbian