Igor

This is fix, just perhaps too noisy. If you don't want to see those messages, change this on your system: https://github.com/armbian/os/commit/36fc679bbb38cdff4223e14a0552c638f577d56b Without you will have your HA always unhealthy. Background: https://github.com/home-assistant/supervisor/issues/4381 This should happen only once after reboot. As we are running a vendor kernel on those devices, there could be issues beyond our control. Once LTS kernel will be available for this HW, we recommend to switch to it. I am running HA, with the exact same method, on Odroid N2 running mainline kernel. Everything works perfectly stable for months.

This package is hosted at our repository, you can delete the list: sudo rm -f /etc/apt/sources.list.d/githubcli.list For the Firefox, I have to check. Our package should be snapd free. Perhaps try to uninstall firefox, remove snapd and install firefox again (should be downloaded from armbian repo).

Should be fixed with: https://github.com/armbian/scripts/commit/9fe944b9c275116a1811f24c76714846ced39f50

Interested perhaps in becoming official maintainer?

Yes, this automation is certainly not accurate, but cuts away some nonsense such as building Gnome or KDE Neon images for entry level sbc, regardless of memory. While XFCE is always there ... I don't mind in any way, its just optimisation of ready-made images.

Not with Armbian. Please provide logs.

Same problem here:

No, it doesn't. This needs to be done beyond. sudo apt purge linux-image-legacy-sunxi64 linux-dtb-legacy-sunxi64

Remove -legacy- kernels from the system.

This logic: https://github.com/armbian/os/blob/main/.github/workflows/recreate-matrix.yml#L185-L201 determines section. "slow-hdmi" is reserved for armhf by default, but I guess we could extend this for several entry level arm64, just how? https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml#L108 and those "slow-hdmi" only gets XFCE desktop.

There has been several recent changes in the Rock S0 support, which were not in those images yet. Is that bad or not, I don't know. Follow other changes that are waiting https://github.com/armbian/build/pulls and once merged, make an image, by adding a HA extension https://docs.armbian.com/Developer-Guide_Build-Switches/#advanced or try this way https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#install-home-assistant on top of Armbian Bookworm with Network Manager networking extension (this is requirement for HA to work).

Did you perhaps tried CURRENT, 6.6.y ? ... here is more to check if 3d rendering works, which is needed at Cina / Gnome. Performances are as they are, its an old horse.

Chromium on Debian is reported broken upstream and there is nothing we can do about except forwarding you this information https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088162 If you are not an expert, use recommended download options, Ubuntu Noble, where we control Chromium and where it works. Be happy that we are able to provide you that (only working) option. Here you can make a donation.

This was moved under a switch to prevent users for switching into kernels that are not meant for end-users. https://github.com/armbian/build/blob/main/config/boards/rock-5b.conf#L7 And this https://github.com/armbian/configng/blob/main/tools/modules/system/switch_kernels.sh is the logic for anyone that might to change / improve this.

Single board computers and especially TV boxes are meant for advanced Linux users due to random low level support. Here you can surely learn a lot about Linux internals, but Linux users experience, if you want to use computer for daily tasks, will be better if you start with a mainstream Linux: https://www.armbian.com/uefi-x86/ https://www.armbian.com/rpi4b/ Also worth reading: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first/

This was not designed by Armbian. I replied here: https://github.com/armbian/configng/issues/265#issuecomment-2487678726 Workaround: remove armbian-config package, upgrade to Bookworm, and install it again.

https://rsync.armbian.com/oldarchive/rk322x-box/archive/

What about the most important logs? armbianmonitor -u

Try to update to most recent, try older versions ... If you use EDGE kernels, then you are at the edge and crashing is expected. EDGE is meant for experimenting, trying new HW features. But like @Werner already asked, we need to see logs. Without is not possible to help. For this hardware its recommended to use this image https://dl.armbian.com/khadas-edge2/Noble_vendor_gnome-kisak with preinstalled browser. Anything else is calling for troubles. BTW. This super complex application is developed by https://www.chromium.org/chromium-projects/ and if anyone can debug, are they.

Simple: sudo apt install google-chrome-stable But. Google does not provide Chrome for hardware you have and Armbian nor Ubuntu can't help.

It does work. Sometimes. Out of lets say 1000 packages that are on your OS, you are telling people, who are maintaining 3 of those (that only deals with hardware aspects), to fix a problem on all 1000. Making an OS better then Debian in user-space sense, deal with tens of thousands of packages, that is another level. We "hack" this by providing you Armbian assembled from Ubuntu packages / repo. Which might be better in this. Becoming yet another maintainer of all free software packages is insane. And there is no warranty to control this process better. Exactly. Try upgrade, but be ready to start from a new image is the only advise that is realistic. Personally, I don't even try. When its time to move to a new point release, I do a backup of dot files following by fresh install. What I need to run, I do it with help of scripts & armbian-config, running apt. It takes less time then upgrade, which has great chances of failure. apt.security folder was removed from upstream, from Debian main repo, to tell you that distro is EOL and there are no more security updates of (Debian assembled) packages. Once Debian maintainers decides to stop, there is nothing we / anyone can do about. Some distros claims to maintain this longer, but in reality it only has marketing / sales value. Update and signing mechanism has been changed, not by us, but by upstream. At different time at different user space. If we fix for one, we have to fix for all. There is another aspect of why this software is not perfect. We are heavily under-staff since ever and there is close to no public funding to mitigate this. Join the project, dig into this upgrade problem, and (try to) fix it. Or at least improve, try many of possible scenarios and write instructions of best practices. Not for me/us, but for someone that might run into this.

Yes, that's correct one.

We don't ship Docker by default. Make no sense to bloat users pace, if we have a tool for install / uninstall. If you have already upgraded to v24.11, then it goes this way: https://docs.armbian.com/User-Guide_Armbian-Software/Containers/ armbian-config --cmd CON001

From this I can only see that you are using a code that is not supported on a hardware that is not supported. For some reason you have two kernels installed, legacy and current, and this is causing randomness at upgrade. Uninstall one variant alongside with DT and headers if installed. And upgrade to Buster, or rather start with a clean Bookworm image.