Jump to content

Armbian 22.11 (Goral) Release Thread

Igor

By Igor
in Armbian Project Administration

 Share

Recommended Posts

Igor

Igor

Posted
Posted
  • Release Candidate Code Freeze Date: 2022-11-16
  • Release Planning Meeting Date:  skipped, forum only - post concerns to this topic 
  • Release Date: 2022-11-28  2022-12-03
  • Release Coordinator: Igor

 

Board maintainers @Contributor/Maintainer please check status of your board. Report a bug or try to fix it by the final release date.

 

Developers, check if your contribution is recorded in Jira as otherwise it won't fit into the release log:
https://armbian.atlassian.net/projects/AR/versions/10012/tab/release-report-all-issues

 

64 Issues in version

61 Issues done

0 Issues in progress

3 Issues to do

 

This release should be in bug fix mud as we stay at 5.15.y / 5.19.y for CURRENT kernel branches.

Igor

Igor

Posted
  • Author
Posted

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

 

Werner

Werner

Posted
Posted

Am I the only person thinking that having a window of one week for maintainers to test RC images, collect feedback (if we get any valuable in that short time window at all) and even then try to attempt fixing reported issues on a "maintenance/bugfixing release" is a bad idea?

TheLinuxBug

TheLinuxBug

Posted
Posted

@Igor

 

I think the better approach would be to use the RC testing form which was made for this, those who can test, please do so and submit your testing forms at: https://www.armbian.com/rc-testing/ 

 

Note: it has been updated to allow you to submit up to 2 image tests at a time, so please take advantage of this if you need to.

 

Thanks.

 

Tagging some people just  to make sure they see this....

@Teslacreiste @balbes150 @teknoid @jock @jethome @ZazaBr @Heisath @littlecxm @schwar3kat @NicoD

 

NicoD

NicoD

Posted
Posted

I tried my VIM3 but the damn thing doesn't seem to be working anymore. I dropped it a few weeks ago. Tried it for the first time now and no boot. The LED goes off every 2/3 seconds as if it's trying to boot again.

I tried Khadas image, different sd-cards. All the same, also not booting from eMMC...
So I guess I'll have to be cut from the maintainer list for VIM3.
I'll try the VIM2, BPiM5, P1, N2+ and Odroid C2 tomorrow.

Igor

Igor

Posted
  • Author
Posted
  On 11/17/2022 at 8:37 PM, NicoD said:

So I guess I'll have to be cut from the maintainer list for VIM3.

Expand  


Make a PR here https://docs.armbian.com/Release_Board-Maintainers/ so we have an actual picture.

 

  On 11/17/2022 at 7:05 PM, TheLinuxBug said:

I think the better approach would be to use the RC testing form

Expand  


Yes ofc. It is important we start with testings.

 

  On 11/17/2022 at 3:24 PM, Werner said:

if we get any valuable in that short time window at all

Expand  


As we spoke, I am fine with postponing release date in order to not compromise quality of release too much. 

balbes150

balbes150

Posted
Posted
  On 11/17/2022 at 7:05 PM, TheLinuxBug said:

I think the better approach would be to use the RC testing form which was made for this, those who can test, please do so and submit your testing forms at: https://www.armbian.com/rc-testing/ 

Expand  

I tried to fill in this form, it is overloaded. It is enough to do - the device name, image, switch works \does not work (free format text field (if it works, filling is not required). For those who want to fill in extended information - add a switch that will open additional fields (for those who want to fill them in).

 

 

Station  P1 - works

Station M1 - u-boot is not working properly, there will be a fix in the near future

Igor

Igor

Posted
  • Author
Posted
  On 11/18/2022 at 9:15 AM, balbes150 said:

Which branch of the official GIT do I need to check

Expand  


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

balbes150

balbes150

Posted
Posted

Jetson Nano core 5.19 is working, core 6.0 is non-working (this problem has been present for a long time, there are no solutions yet).

schwar3kat

schwar3kat

Posted
Posted

orangepizeroplus works:
Armbian_22.11.0_Orangepizeroplus_jammy_current_5.15.79.img.xz
Armbian_22.11.0_Orangepizeroplus_bullseye_current_5.15.79.img.xz

RC testing form submitted

schwar3kat

schwar3kat

Posted
Posted

orangepi-r1 works. iperf values as expected:

Armbian_22.11.0_Orangepi-r1_jammy_current_5.15.79.img.xz
Armbian_22.11.0_Orangepi-r1_bullseye_current_5.15.79.img.xz


RC testing form submitted

Igor

Igor

Posted
  • Author
Posted

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.

balbes150

balbes150

Posted
Posted
  On 11/18/2022 at 12:21 PM, Igor said:

I will merge it to v22.11 right before rebuild.

Expand  

I cloned the last MASTER, built an image for Station M3, checked, DTB is available, everything works. It is strange why there is no DTB in the RC image, perhaps it is assembled from "old" packages from the repository (there is no package with DTB)? At the same time, I checked the build of a variant with integrated DTB in the kernel package. Everything works. I can send a PR with patch fixes for a new version of the core package for M3 with one package for the core and DTB (just as it is implemented for the "media" core).

Igor

Igor

Posted
  • Author
Posted
  On 11/19/2022 at 7:57 AM, balbes150 said:

It is strange why there is no DTB in the RC image, perhaps it is assembled from "old" packages from the repository

Expand  

 

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

Igor

Igor

Posted
  • Author
Posted
  On 11/19/2022 at 7:57 AM, balbes150 said:

It is strange why there is no DTB in the RC image, perhaps it is assembled from "old" packages from the repository (there is no package with DTB)?

Expand  

 

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

balbes150

balbes150

Posted
Posted
  On 11/19/2022 at 8:00 AM, Igor said:

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

Expand  

I haven't done PR for M3 for a long time. Therefore, I was surprised why the build worked incorrectly (without DTB).

balbes150

balbes150

Posted
Posted
  On 11/19/2022 at 8:03 AM, Igor said:

I don't follow anymore - media kernel, integrated dt, extlinux, efi ... 

Expand  

You don't have to keep track of anything. I ran the build from the official GIT Master and the build went correctly (DTB files are included and work correctly). It's just not clear why the RC image was obtained without DTB.

Igor

Igor

Posted
  • Author
Posted
  On 11/19/2022 at 8:10 AM, balbes150 said:

It's just not clear why the RC image was obtained without DTB.

Expand  


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

Igor

Igor

Posted
  • Author
Posted

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 ]

 

schwar3kat

schwar3kat

Posted
Posted

orangepi-r1plus-lts works. iperf values as expected:

Armbian_22.11.0_Orangepi-r1plus-lts_jammy_current_5.15.79.img.xz
Armbian_22.11.0_Orangepi-r1plus-lts_bullseye_current_5.15.79.img.xz
 

RC testing form submitted

jock

jock

Posted
Posted
  On 11/19/2022 at 6:33 AM, Igor said:

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.

Expand  

Tested Orange Pi 4 LTS with both debian bullseye and jammy images, it booted in all attempts except one attempt where apparently the HDMI monitor did not turn on (led was blinking so kernel was alive).

Unfortunately I had no serial attached and when I attached the serial, it never occurred anymore.

balbes150

balbes150

Posted
Posted

All versions (Station M2\P2\M3) with LEGACY kernel cannot run DE. The reason is the incompatibility of the 3D packages and the legacy kernel. Fixing this bug  #4467

Igor

Igor

Posted
  • Author
Posted

Release delayed for (at least) one week. Health issues + status too unknown.

jock

jock

Posted
Posted

I don't know if it has already been fixed, but the last time I tried the RC images, the Terminator font was huge again.

I tested 32 bit Tinkerboard and 64 bit Orange PI 4 LTS jammy xfce images.

Igor

Igor

Posted
  • Author
Posted
  On 11/26/2022 at 12:53 PM, jock said:

I don't know if it has already been fixed, but the last time I tried the RC images, the Terminator font was huge again.

I tested 32 bit Tinkerboard and 64 bit Orange PI 4 LTS jammy xfce images.

Expand  


I think i know how to fix that ...

 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept