SteeMan

Moved

Glad to hear you got it working. I've gone through the same issues you had in the past when trying upgrades, so the steps were in the back of my mind. It should be fine to now remove the obsolete packages.

So you don't want to remove: armbian-config armbian-firmware armbian-zsh linux-dtb-current-sunxi linux-image-current-sunxi (those last two are your linux kernel and dtb files - which was the reason you couldn't boot previously) So you can see here the upgrade disabled the armbian apt repository. So it can't install the updated armbian packages. So should be: deb http://apt.armbian.com jammy main jammy-utils jammy-desktop (So uncomment and change all references from focal to jammy) That is coming from one of the armbian* files located in /etc. I don't remember which one. If after everything is upgraded, if it still isn't showing the correct value, you can edit. I think this should get updated by the installation of the correct armbian-bsp-* package.

@ezpc98 armbian-config is just automating the setting of the parameters in ArmbianEnv.txt. So after running it, you can see what is set and adjust manually if you prefer.

You would use armbian-config to enable overlays. But in a quick look there is no such overlay in Armbian.

Ive never frozen the kernel when doing upgrades. So that shouldn't be necessary. I would recommend redoing the upgrade, and at the end looking at the list of obsolete packages and not removing them. Finish the upgrade (without removing obsolete packages) then go see what the status of your /etc/apt/sources.d/armbian.list file is and make that correct, then use apt to update/upgrade your armbian packages. Then look at your obsolete packages and make sure the list is sane (that is it's not removing any armbian needed packages, *armbian*, linux-image-* or linux-dtb-*.) Only then would I remove obsolete packages.

Please submit a PR, and this can be discussed there.

I would suggest you use the armbian build system and build the CLI minimal build for your board. That should be sufficient for your needs as a starting point. It is also a low barrier to entry as you can get that working with minimal understanding of what is going on behind the scenes. Then you can dig into the details to learn as you need.

A significant reason that the Raspberry Pis are more expensive is that the manufacturer actually invests time and resources into the underlying software. OrangePi does not. OrangePi takes advantage of the open source community hoping they can get software support for free without contributing much if anything to that process. There is a reason that OrangePi boards are not generally supported by Armbian, and lack of manufacturer support is a big reason. So that means that if you want good software to run on OrangePi boards, then OrangePi expects you to do the work. And that is a lot about what this thread in the forum is about - the community trying to support these boards.

It looks to me like the upgrade is uninstalling the kernel, dtb and likely other armbian packages. Likely because it thinks they are extra for some reason. During the upgrade are you seeing an option to remove old packages? If so look at that list and see if there are any Armbian packages in that list (there shouldn't be) (specifically anything with Armbian in the name as well as linux-image-* and linux-dtb-*) I think successful upgrades disable the Armbian apt repository which should leave all the armbian packages untouched. Then after the upgrade, you manually enable the armbian apt repository for the correct release and then do an apt update/upgrade of the armbian packages.

No clue as I don't have that box. Search the forums for information. As far as build goes, you should be reading the FAQ posts: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

With weekly image builds located here: https://github.com/armbian/community And daily rolling release apt packages (kernel and other armbian packages) located at: beta.armbian.com

I didn't say install, I said ran. If you ever ran coreelec on. The box, which above you said you did from the SD card. That changes the boot environment on the EMMC and makes it incompatible with Armbian.

If you have ever run coreelec on the box, you will not be able to install Armbian. The coreelec changes the boot environment on emmc in a way incompatible with Armbian. You will need to reinstall an original android firmware which will restore the boot environment if you want to install Armbian.

@mc510 You may know this but I'm adding this in case you or others reading this thread don't. This board isn't supported by Armbian. With limited resources Armbian can only support a limited number of boards with their resources. This board is a Community Maintained board, which means that it is up to the people in these forums to submit PRs to maintain and or improve support for this board. What often happens is that no one contributes back to the community and over time Community boards degrade in quality until they no longer build in which case they are set to end of life status. And removed. For the official description on Supported vs Community Maintained see: https://docs.armbian.com/User-Guide_Board-Support-Rules/