Igor

Means nothing. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
 
 
Anyone can adopt it for you.
 
Armbian is free software and provides best effort help through community forums. If you can't find answer there and/or with help of general project search engine and documentation, consider hiring an expert. 

We are already blowing too much for public good and there is nothing coming back:
https://docs.armbian.com/User-Guide_FAQ/#why-is-armbian-constantly-asking-for-money-free-software-should-be-free
 
When / if solution is found, this way its implemented with lowest additional damages https://docs.armbian.com/Process_Contribute/ Of course project problems doesn't stop here. Review process is needed and long term code maintainace also contributes to the costs. Again FAQ: https://docs.armbian.com/User-Guide_FAQ/#support-time

Hi. We have not noticed any problems with the rc at this time.

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

RK3328 Orangepi r1plus lts seems to have reverted to broken LAN0 Ethernet behavior similar to before the commit
Enable rockchip64: XHCI HCD USB TRB ENT quirk for RK3328 #3763
I can't immediately see what the cause is.  The patch works and quirk is included in the dtb.
Same as before, it can be mitigated by disabling tx offload.
I've reset AR1172 to in progress,

@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.

@Contributor/Maintainer If something has to be squeezed into the code ... I guess merging armbian-next has to be postponed. After Sunday, bugs bugs bugs. Solving, not generating new ones  

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!

ok thanks, 
i solved it , no need to change kernel ,
i added in /boot/armbianEnv.txt overlay_prefix=sun50i-h5 which is specific for orange pi zero plus , overlays appeared in armbian-config i selected them ,
i inserted the pa gpio corresponding to the pin connected to the 1wire sensor and everything works.
 

This bug is here for a while.
https://github.com/armbian/config/issues/33
You can enable this manually too.
 

You might need to downgrade kernel to 5.10.y

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.

No I do not think so. The hardware is nearly the same - base is just pro with removed devices.

Yes. I don't think it's even near being merge-able right now, small bugs but are showstoppers for most people, and I can't handle them all by myself in such timeframe, including handling all the Jammy fixes and a dozen rockchip kernels, extlinux, nand-sata-install, etc.
And once merged a whole slew of things will show up (extras buildpkgs, prebuilt, rootfs caching, repo publishing, git bundle stuff, most of the GHA stuff that normal developers hardly ever run).
The concepts behind armbian-next are almost fully realized, but the fruits still have to be collected. Otherwise it seems pointless...
I will keep it rebased as much as possible, so the effort lives on, only without pressure.
Before merge, documentation has to be written too, so that will take a while.
work continues!
 
 

@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:


 

Ban is still in place  I am writing an email right now. In general it would be better to use Google mirror primarily. Or we need to use kernel.org Git for bundles?
 

You mean like having our own full kernel mirror?
 

I would not push on moving everything to distro compilers at once. What works, works and we do this gradually. Going on half now, removing them all in one year. Something like that. Even today, sometimes we will need to deal with a special compiler, so support has to remain. And a few of them if there is too much work with adopting the code.

Thanks for update. Will do another cycle of review when possible.

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!

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

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!

@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:


 

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!

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!

Costs from 2 USD on and its a very valued tool in this world:
https://linux-sunxi.org/UART

"Delete My Account"
https://forum.armbian.com/terms

@Moderators

TinkerBoard Asus:
 
 
 
 
RockPro64:
 
 

"Delete My Account"
https://forum.armbian.com/terms

@Moderators

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