Armbian 23.02 (Quoll) Testings

Igor · February 13, 2023

In order to get best possible support status, please help us with testings. This last testing phase is a final check to see if devices boots and if basic functions work. We can only fix minor issues, try to recreate or remove broken images, but its also good if we write down what is wrong https://www.armbian.com/bugs/

Deadline for submitting test report: February 24th

Armbian has its own infrastructure for automated testings. But its limited so we need additional help with manual testings. Results:

- release candidate testings. Images has been uploaded to: https://stpete-mirror.armbian.com/dl/ -> BOARD/rc/

Publish report to:

https://www.armbian.com/rc-testing/

or comment below.

(I have manually tested Odroid N2+, Rockpi 4 1Gb)

@Contributor/Maintainer

In order to get your work into the release log, add a title, URL to commit / PR and set "Fix version" to 23.02

schwar3kat · February 13, 2023

Suggestion: allow more than two images per board in the RC testing form.

schwar3kat · February 13, 2023

Orangepi-r1plus-lts tested success:
Armbian_23.02.1_Orangepi-r1plus-lts_bullseye_current_5.15.93.img.xz
Armbian_23.02.1_Orangepi-r1plus-lts_bullseye_current_5.15.93_minimal.img.xz
Armbian_23.02.1_Orangepi-r1plus-lts_jammy_current_5.15.93.img.xz

All images tested and working as expected.
Iperf performance is as expected in both directions on both ports simultaneously.
2 images listed on RC testing form (minimal build left off).

schwar3kat · February 14, 2023

Orangepi-r1 tested success:
Armbian_23.02.1_Orangepi-r1_bullseye_current_5.15.93.img.xz
Armbian_23.02.1_Orangepi-r1_bullseye_current_5.15.93_minimal.img.xz
Armbian_23.02.1_Orangepi-r1_jammy_current_5.15.93.img.xz

All images tested and working as expected.
Iperf performance is as expected in both directions on both ethernet ports simultaneously.
Wifi works.
2 images listed on RC testing form (minimal build left off).

schwar3kat · February 14, 2023

Orangepizeroplus tested success:
Armbian_23.02.1_Orangepizeroplus_bullseye_current_5.15.93.img.xz
Armbian_23.02.1_Orangepizeroplus_bullseye_current_5.15.93_minimal.img.xz
Armbian_23.02.1_Orangepizeroplus_jammy_current_5.15.93.img.xz

All images tested and working as expected.
Iperf performance is as expected in both directions on ethernet and wifi ports simultaneously.
2 images listed on RC testing form (minimal build left off).

Igor · February 14, 2023

Found a problem:
Radxa Zero generates EDGE images instead of CURRENT

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

Efe Çetin · February 14, 2023

Tested:

- Armbian_23.02.1_Orangepi5_jammy_legacy_5.10.110_minimal.img

- Armbian_23.02.1_Orangepi5_jammy_legacy_5.10.110_cinnamon_desktop.img

USB-A ports, HDMI, ethernet port and sound seem working properly.

going · February 14, 2023

Tested:

Armbian_23.02.1_Bananapim64_jammy_current_5.15.93_minimal.img

The first start, boot, reboot is normal.
Found not included in the fix for "armbianmonitor" for one cluster.
Corrections here

ALIGMSTEN · February 14, 2023

Tested:

Armbian_23.02.1_Orangepizero2_bullseye_edge_6.1.11.img.xz

Normal, first start, boot and reboot.

DT known parts missing as expected.

htop - can add temp and cpu frequency, however not in DT (forgot to check version)

Armbian_23.02.1_Orangepizero2_bullseye_legacy_4.9.318.img.xz

Does not boot. (am sure serial output will be booti error - will check if you need)

boot.cmd is incorrect (copied direct from image sd card)

# DO NOT EDIT THIS FILE
#
# Please edit /boot/armbianEnv.txt to set supported parameters
#

# default values
setenv load_addr "0x45000000"
setenv overlay_error "false"
setenv rootdev "/dev/mmcblk0p1"
setenv verbosity "1"
setenv rootfstype "ext4"
setenv console "both"
setenv docker_optimizations "on"
setenv bootlogo "false"

# Print boot source
itest.b *0x10028 == 0x00 && echo "U-boot loaded from SD"
itest.b *0x10028 == 0x02 && echo "U-boot loaded from eMMC or secondary SD"
itest.b *0x10028 == 0x03 && echo "U-boot loaded from SPI"

echo "Boot script loaded from ${devtype}"

if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then
	load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt
	env import -t ${load_addr} ${filesize}
fi

if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi
if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi
if test "${bootlogo}" = "true"; then
	setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}"
else
	setenv consoleargs "splash=verbose ${consoleargs}"
fi

# get PARTUUID of first partition on SD/eMMC it was loaded from
# mmc 0 is always mapped to device u-boot (2016.09+) was loaded from
if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi

setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}"

if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi

load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
fdt addr ${fdt_addr_r}
fdt resize 65536
for overlay_file in ${overlays}; do
	if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then
		echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo"
		fdt apply ${load_addr} || setenv overlay_error "true"
	fi
done
for overlay_file in ${user_overlays}; do
	if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then
		echo "Applying user provided DT overlay ${overlay_file}.dtbo"
		fdt apply ${load_addr} || setenv overlay_error "true"
	fi
done
if test "${overlay_error}" = "true"; then
	echo "Error applying DT overlays, restoring original DT"
	load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
else
	if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then
		echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)"
		source ${load_addr}
	fi
	if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then
		load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr
		echo "Applying user provided fixup script (fixup.scr)"
		source ${load_addr}
	fi
fi

load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd
load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image

booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

going · February 14, 2023

6 минут назад, ALIGMSTEN сказал:

htop - can add temp

htop --version on bullseye ?

ALIGMSTEN · February 14, 2023

Generating locales: en_ZA.UTF-8
root@orangepizero2:~# htop --version
htop 3.0.5
root@orangepizero2:~#

going · February 14, 2023

55 минут назад, ALIGMSTEN сказал:
htop 3.0.5

It has no functionality for processor frequency

@ALIGMSTEN Alistair, can you add patches that you have running on the 5.19 kernel for the 6.1 kernel?

ALIGMSTEN · February 14, 2023

@going and @Igor checking the H616 mainlining thread, the x_late patch is running currently unoptimized WIP, we can improve on this as testing play's out. I will add the recommended thermal changes for now and can submit a pr to 6.1 they will be fine if that is good.

Igor · February 14, 2023

Another checks:

- Nanopi M4v2, install to internal eMMC / NVMe root
- Opi3 LTS bullseye https://paste.armbian.com/facogodope

Igor · February 15, 2023

A problem with Odroid C2 - stuck on reboot - was reported. It's one of those: Here we go again

jock · February 15, 2023

Tested OrangePi 4 LTS:

Armbian_23.02.1_Orangepi4-lts_jammy_current_5.15.93_xfce_desktop.img.xz
Armbian_23.02.1_Orangepi4-lts_bullseye_current_5.15.93_minimal.img.xz

Bluetooth adapter is detected, but this time I was unable to pair with the usual audio speaker

The rest seems to work pretty well

jock · February 15, 2023

Tested Asus Tinkerboard:

Armbian_23.02.1_Tinkerboard_jammy_current_6.1.11_xfce_desktop.img.xz

Most of the hardware seems to work pretty fine and the board is stable.

Bluetooth adapter is not detected at all (perhaps some kernel config bits are missing? Need to check this...).

I got a weird stack trace when launching the "Celluloid" application, but it seems more a kernel bug rather than anything related to armbian.

An old 2Gb USB stick did trigger lot of weird USB errors, the stick works perfectly elsewhere, perhaps some compatibility issues. Overall, USB ports are working with other devices.

Wireless performance is swinging from 1 mbps to 12 mbps, not really clear why, but connection is stable.

Igor · February 17, 2023

@Contributor/MaintainerTomorrow (Saturday 18th, we will start moving armbian-next into main). @rpardini and me will be around whole (our) day as there is some work and troubles are expected. We need to adjust and test CI and in case someone has no other plans for Saturday, welcome for assistance. Thanks.

going · February 17, 2023

I sincerely wish you gentlemen good luck.

SteeMan · February 21, 2023

I tested the 23.02.1 aml-s9xx-box builds against all the amlogic TV boxes I have and they worked as expected.

Igor · February 21, 2023

- build framework switched today

- OK, we are going out with this. Rsync mirror is pushing at average of 1GBbit/s + for a whole day

- short video about release was recorded today

- release announcement is in the works

balbes150 · February 22, 2023

These models are not listed on the report page.

BananaPI r2pro - work

Khadas EDGE2 - work

Herc · February 25, 2023

none of the images from https://www.armbian.com/odroid-c2/ seem to boot at all
(tested: Armbian 23.02 Bullseye CLI and Jammy Gnome desktop on two SBCs)

img burnt, power connected, blank screen, no blue LED "heartbeat" blinking.

previously Armbian_23.02.1 from ../rc/ booted ok

(just had that "no reboot" issue)

Edited February 25, 2023 by Herc
typo

Herc · February 27, 2023

Armbian_23.02.1_Odroidc2_jammy_current_6.1.14.img.xz (from imola.armbian.com/dl/odroidc2/ )

boots from SD, but still no reboot

Herc · March 8, 2023

the odroid c2 reboot (kernel-) issue was reported in 2022 already, some say it was fixed in c4 (?).

https://forum.armbian.com/topic/20241-odroid-c2-never-starting-after-a-soft-reboot-reboot-command/

Sign In

Armbian 23.02 (Quoll) Testings

Recommended Posts

Igor

schwar3kat

schwar3kat

schwar3kat

schwar3kat

Igor

Efe Çetin

going

ALIGMSTEN

going

ALIGMSTEN

going

ALIGMSTEN

Igor

Igor

jock

jock

Igor

going

SteeMan

Igor

balbes150

Herc

Herc

Herc

Forums

My Activity Streams

Download

Store

Important Information