Igor

- 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

Try release candidate images (safe to use them in case they work fine) from here: https://stpete-mirror.armbian.com/dl/bananapim5/rc/ and follow instructions from https://www.armbian.com/bananapi-m5/

Orangepi-config is fork of armbian-config but they are assembling images with some older version of armbian build script. It was fixed. https://github.com/armbian/config/pull/187 You don't need to do anything else, but to wait for release, planned for end of next week.

Change bionic to jammy in /etc/apt/sources.list.d/armbian.list and it should probably be fine.

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

I think we don't update Bionic repositories anymore ... but plan is to move to common as those packages are identical on different releases.

Strange thing that software author was actually testing this on Armbian and now it doesn't work properly. Well, I would suggest pinging author(s). "Flash a MicroSD card with the latest armbian image." https://simpnas.com/docs.php @Tido Long time no see.

Please try with armbian-next https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ Current master branch is going towards EOL soon. If we have a bug, it will only be fixed in the new system. Worse case use a workaround - remove it withing build script - remove file patch/kernel/archive/sunxi-6.1/patches.armbian/arm64-dts-sun50i-h6-orangepi.dtsi-Rollback-r_rsb-to-r_i2c.patch

Welcome to Armbian community support. This is pretty step step This also means you need to get familiar with some facts first https://docs.armbian.com/User-Guide_FAQ/ If our image is broken, then re-branded image into Dietpi (stealing credits and abusing support is most used way of piracy in free licence software world) images are usually also broken. Small chances, but worth trying. A new release is coming out, but there is little we can do in few days before new release. Even removing this board from the download pages represent some efforts, so others won't waste their time trying broken images. Unless someone steps up, donate his time to fix a problem and asks if there is anything to help out.

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

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

Tried with another device (Opi 3 LTS with similar kernel, same user land) and can't reproduce. https://paste.armbian.com/facogodope I don't have Renegade - @TonyMac32 any clues if HW would played any role in this?

Found a problem: Radxa Zero generates EDGE images instead of CURRENT https://github.com/armbian/build/pull/4833

Can you check if those images behaves better https://stpete-mirror.armbian.com/dl/renegade/rc/

PMU on Orangepi 3LTS is Allwinner AXP805, so perhaps checking those pages: https://linux-sunxi.org/H6 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/mfd/axp20x.c?h=v6.1.11 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/allwinner/axp803.dtsi?h=v6.1.11 and board DT, patches & modifications from: https://github.com/armbian/build/tree/master/patch/kernel/archive/sunxi-6.1 Where is the problem? No idea.

This will spare you some: https://www.armbian.com/newsflash/code-freeze-and-moving-to-new-framework/ Many supports it on paper, but on very few SoCs actually works well. On each kernel upgrade, functions breaks down and all users care is complaining about, while we are loosing thousands of hours for keeping devices operational. If they are unable to answer on cheapest possible way to all at once, in public, (community forums are here to provide this support as any other is not possible), do you think they will answer on a lot more expensive private ways? We could easily lost daily 10 hours if we would respond to our users emails / PM. Since we have no option to hire technical support staff, questions are replied with canned message / deleted. I assume vendors receive about 10 - 20 x our quantity and IMO they also can't cover. Welcome!

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

You do understand that you can't remove SD card? Not yet, as boot loader for SPI that would be able to boot modern kernel directly is not developed yet. Otherwise it should be plain simple: armbian-install, then SD card boot, nvme root ...

Because nobody volunteered to try, check for possible regressions and submit changes? From project perspective, if @Heisathdon't have much time and interest, there is nothing we can do as project is way way too small to follow endless users & HW needs. We don't have a backup.

To change display resolution, add below to the /boot/armbianEnv.txt: extraargs=video=HDMI-A-1:1920x1080M@60

Kernel is defining hardware features. Which kernel are you using in "Ubuntu"?

We will continue to provide kernel updates for imx6 (Cubox-i and Udoo) and other 32bit devices, just quality assurance won't be applied anymore. For matured support, as in this case, this is usually not a problem. Migration is possible, but not on OS (different arhitecture & different boot process) but application level - copy data and configuration for nginx, then copy data and config for samba/nfs ...