Jump to content

Armbian 22.02 (Pig) Release Thread

Heisath

By Heisath
in Armbian Project Administration

 Share

Recommended Posts

piter75

piter75

Posted
Posted
13 hours ago, Igor said:

rockchip64 current still needs to be bumped to 5.15.y 

I gave it a shot tonight and well... edge and current diverged quite a bit functionally between themselves :( during my absence ;).

With as much time as I can spare on it at the moment I am not confident enough that I can synchronise them correctly during the next 1-2 evenings.

@Igor Do we consider keeping rockchip64 current at 5.10.y for this release?

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
31 minutes ago, piter75 said:

Do we consider keeping rockchip64 current at 5.10.y for this release?

 

EDGE is tested to some degree ... people that needs 5.10.y will be able to downgrade and freeze. So, we have an emergency path.

 

5.15.y upgrade on current is not at all cost. We will not upgrade meson64 as well. I would set deadline to wednesday, but I leave this call to @Heisath

 

@balbes150 station m2 legacy kernel fails.
 

Spoiler 
  ./compile.sh \
  BETA="yes" \
  RELEASE="bullseye" \
  KERNEL_ONLY="no" \
  SKIP_EXTERNAL_TOOLCHAINS="no" \
  DESKTOP_ENVIRONMENT_CONFIG_NAME="" \
  BUILD_DESKTOP="no" \
  BUILD_MINIMAL="no" \
  DESKTOP_ENVIRONMENT="" \
  KERNEL_CONFIGURE="no" \
  BOARD="station-m2" \
  RC="yes" \
  LOG_SUBPATH="debug/station-m2" \
  BRANCH="legacy" \
  MAKE_FOLDERS="yes" \
  IMAGE_PRESENT="no" \
  USE_MAINLINE_GOOGLE_MIRROR="yes" \
  ARMBIAN_CACHE_TOOLCHAIN_PATH="${ARMBIAN_CACHE_TOOLCHAIN_PATH}" \
  ARMBIAN_CACHE_ROOTFS_PATH="${ARMBIAN_CACHE_ROOTFS_PATH}" \
  REPOSITORY_INSTALL="armbian-bsp-desktop,armbian-desktop,armbian-config,armbian-firmware,armbian-zsh" \
  DESKTOP_APPGROUPS_SELECTED="$DESKTOP_APPGROUPS_SELECTED" \
  EXPERT="yes"

 

 

Other troubles:
https://github.com/armbian/build/actions/runs/1830500410

 

Link to comment
Share on other sites
Igor

Igor

Posted
Posted

RC builds are available on one server only under $BOARD/rc/
https://imola.armbian.com/dl/ (sorry its not very fast and using CDN for this is too big waste of traffic)


We need to check two things:
- are we producing correct targets and why some are failing ? (I am working on that, sometimes its just network issue and we just do it again)

- are they working? We don't need to test all images. For example - if there is desktop Jammy XFCE image, test one, other builds are optional. I count that some will prefer Debian based, so he will test that. Remember that builds are already tested via automation to some degree.

What kind of build targets do we want? (this is related to specific hardware)

For example:
https://imola.armbian.com/dl/bananapi/rc/

- Focal XFCE desktop with 5.15.y

- Jammy XFCE desktop with 5.15.y (next LTS userland)

- Focal CLI with 5.15.y
- Bullseye CLI (we need at least one Debian variant)

- SID CLI (Debian rolling release with EDGE kernel) This image is almost like nightly build - it gets latest daily armbian kernel and latest packages from upstream


IMO this is a perfect minimum for general purpose device.

 

https://imola.armbian.com/dl/pinebook-pro/rc/

Might only need 4 desktop builds. One on more conservative side (LTS kernel), other perhaps SID with EDGE?

 

https://imola.armbian.com/dl/orangepizero/rc/
Possible changes: 
Jammy EDGE -> sid EDGE

 

...


This list represent what will show up on the download pages:

https://github.com/armbian/build/blob/master/config/targets.conf

and has to be finalized.

 

@yang We need to get some involevement from maintainers to check if build targets are appropriate (not too much not too little) and if builds are working. They should, but we are not 100% sure.

Link to comment
Share on other sites
piter75

piter75

Posted
Posted
On 2/12/2022 at 1:34 PM, Heisath said:

Yeah,  I will move the RC branching a few day, also the release will be moved 1-3 days on Igors request.

I did not make it to send the PR yesterday although prepared the switch.

I am totally unsure however how PineBook Pro fares after the switch (the changes are pretty substantial) so we should probably keep rockchip64-current at 5.10 and catch-up after the release.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
50 minutes ago, piter75 said:

I am totally unsure however how PineBook Pro fares after the switch (the changes are pretty substantial) so we should probably keep rockchip64-current at 5.10 and catch-up after the release.


Here we have two builds with 5.15.y kernel and Jammy desktop

https://imola.armbian.com/dl/pinebook-pro/rc/

 

Ping @yangPinebook Pro maintainer.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
2 minutes ago, balbes150 said:

Did I understand correctly that with the latest bootsplash patches, the SKIPBOOTSPLASH option is no longer needed for kernel 5.16\5.17  ?


Correct. Bootsplash works again on 5.16.y 

Link to comment
Share on other sites
TRS-80

TRS-80

Posted
Posted
On 2/14/2022 at 7:33 AM, Igor said:

We need to get some involevement from maintainers

 

I am not sure all the new Maintainers are even members of the appropriate group(s) (here on forums, I mean) to work with that group mention, above.  I was meaning to make sure they were all aligned with Board Maintainers (which I have been keeping up to date) but did not get to it yet.  I will try and do so ASAP (like tonight or tomorrow I guess).

Link to comment
Share on other sites
teknoid

teknoid

Posted
Posted

The mainline sunxi sets the cpufreq to 1,3 GHz on the nanopineoplus2. This is too fast for the older models. I would like to seed a /etc/default/cpufrequtils file with reduced MAX_SPEED. Where can I place it inside the armbian build process? Or do you have another idea how to initially reduce the max cpu speed?

 

And btw. could you please reenable the automatic build for nanopineoplus2. I already set status to "supported" on the board page. But I belive there is something magic to bring this back.

 

 

Link to comment
Share on other sites
Heisath

Heisath

Posted
  • Author
Posted

If possible it would be great if all maintainers could send a PR with fixed tag for kernel source.

Follow this PR https://github.com/armbian/build/pull/3500

This would allow for more reproducible builds.

 

This together with Igors suggestion of merging 

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

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

could go into a new RC branch.

 

 

@Contributor/Maintainer

 

1
Link to comment
Share on other sites
Igor

Igor

Posted
Posted

I'll make another RC in a couple of hours which can also be a release build. In case no major troubles are found ... 

@Heisath Anything else? In jira we have to move undone tasks further and release, release docs are also getting into close to done state. 

Link to comment
Share on other sites
Heisath

Heisath

Posted
  • Author
Posted

Hi.

 

Release day is today. I see most boards have fixed kernel versions now, thats great!   @Igor did you produce a new RC as stated yesterday?

 

Otherwise we can IMHO go straight to release. Quickly checking the diff between master and v22.02-RC there seems to only be a limited amount of new commits (and those all look like bugfixes/kernel tag fix). Shall we produce the release from master? 

 

 

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
55 minutes ago, Heisath said:

did you produce a new RC as stated yesterday?

 

yes.

 

56 minutes ago, Heisath said:

Otherwise we can IMHO go straight to release.

 

also stable images are ready. Uploading will take hours ... and I need to check with @TRS-80 if document is ready to go.

 

56 minutes ago, Heisath said:

Shall we produce the release from master? 

 

Yes, but branch it for bugfix release. That shell go out from there.

Link to comment
Share on other sites
TRS-80

TRS-80

Posted
Posted

Good morning, guise!

 

I made some major revisions all day yesterday after getting some helpful feedback from @rpardini.  Which made it a little long again.

 

With a good night's sleep now and a fresh cup of coffee, I will keep polishing it up / paring it back down right up until you forcibly yank it from my clutches, but it is mostly ready to go I think.  :)

 

 

1
Link to comment
Share on other sites
Heisath

Heisath

Posted
  • Author
Posted

Release is in the works. I have moved the unfinished issues in Jira to the next release (22.05), pushed the release button. 

 

Release branch is https://github.com/armbian/build/tree/v22.02

 

TRS-80 is finalizing release notes to post. @Igor will build final images.

 

Thanks all for contributing!

 

 

Release notes from JIRA:

 

Release notes - Armbian - Version 22.02

 

Bug

AR-1101 DRM patch is failing on Rockchip

AR-1079 Ubuntu archive redirector is not providing best service

AR-1077 Fix RPi4 userland audio

AR-1069 First login doesn't pick up correct shell

AR-1065 Twitter forum registration is not working

AR-1063 X86 desktop images are not enabled in CI

AR-1062 When selecting repository install u-boot might not be flashed

AR-1055 Aptly repository seems to be out of business

AR-1048 Rpi kernel image is not updated on upgrade

AR-1043 linux-firmware repository change branch from "master" to "main"

AR-973 Helios64 boot building is failing after update to 2021.10

AR-871 Debian SID broken wallpaper

Story

AR-1074 Switch all CURRENT to 5.15.y and EDGE to 5.16.y

AR-1009 Armbian Framework extensions and UEFI support

Task

AR-1100 Support for Orange Pi R1 Plus LTS, Drivers for YT8531 and other Motorcomm chips. Linux-5.10y and Linux-5.15y.

AR-1084 Enable 3D support on Debian desktop

AR-1078 Add additional forum plugins and adjust settings

AR-1068 Add gnome-system-monitor to Focal and Jammy

AR-1049 Add ZFS that supports kernel 5.15.y

AR-1044 Improve Raspberry Pi support

AR-1041 JetHome: fix brcm (AP6255) firmware links

AR-1040 Refactor armbian-bsp-cli package creation

AR-931 Using Docker image for building kernels

AR-893 Cleanup rockchip64 u-boot scenarios

AR-757 Adding Raspberry Pi

AR-586 Implement fan controller for Nanopi M2V2

Link to comment
Share on other sites
  • Igor unpinned this topic
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept