Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Armbian 23.02 (Quoll) Testings

Igor
in Armbian Project Administration

Featured Replies

 

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:

 

quoll-auto-tests.png

 

- 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

  • Igor changed the title to Armbian 23.02 (Quoll) Testings
  • Igor unpinned this topic

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

    • 1
    • Igor pinned and featured this topic

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

    • 1

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

    • 1

    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

     

    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

    • 1

    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.

     

     

     

    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 by Herc
    typo

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

    • 1
    • Igor unpinned this topic
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.