Igor

If you plan to start from scratch and you don't want to wait hours until repository is updated, yes, rather download and use latest image. Upcoming fix will solve this problem for everyone that still use old image.

Packages are in the update process - few hours from now it will be ok.

Some chips used in those usb2sata adaptors have issues combined with issues that are present on USB3 stack on some SoCs = troubles. Generally, USB3 storage solutions are to be avoided if possible.

Board usually shuts down in case it reached critical temperatures. Can you add a heatsink?

- there are several revisions of Rock64 and not all work so the problem is similar to cheap TV boxes, which are assembled from random hardware parts - released images (at least Debian minimal) work on my revision, however I didn't test HDMI output Try attaching serial console to see where it stops, check if it gets up on the network ... perhaps its "just" broken HDMI.

Once PR is merged, automated nightly beta repository has this kernel within hours.

Sadly no. https://github.com/armbian/build/tree/main/config/boards There are (too) many boards in the system, added by random people (this is build system and we accept anything that builds, but we don't maintain those boards as we can't afford associated costs / there are not enough resources), but only supported / .conf are recognized until there is someone willing to maintaining them and fits condition of "supported" board. When we find out that conditions are not met anymore, they are "un-recognized". Support is defined under those rules: https://docs.armbian.com/User-Guide_Board-Support-Rules

Welcome to custom hardware / division exotics / subdivision retro It is hard already when its new custom hardware and main division. If nobody ported HW to mainline Linux and keep it operational, its usually quite a long path. Armbian provides build framework, that helps in the process, but hard work is still on the one that will deal with the SoC - here you can hope to find someone on forum(s) to share some specific ideas. Adding is fairly straightforward https://docs.armbian.com/Process_Contribute/#adding-a-new-board but if there are sources for boot loader, sources for kernel, or better - support in the mainline kernel. Even when you have all this, it can still be quite challenging. Each such board usually require more people, a team. When I recall how many months we lost on one of Marvell's 🤔 Espressobin is an example how board support can be made super complicated - check history from day one. If board support package is on that level ... its worse out of all we have seen here. And now its an old hardware, not interesting so much. And remain broken as we don't have anyone to deal with it / its not worth.

Feature regressions are expected - Linux kernel is complicated machinery and without spending hours, a day or a week investigating, it's usually not possible to tell. We don't touch Rpi kernels much. We have our own kernel config, but we use official Rpi sources, so I guess 1st step would be looking if someone reported something similar https://github.com/raspberrypi/linux/issues By newer you mean 6.12.y, 6.16.y ... or 6.6.63 ->

I hope you flashed u-boot from armbian-install ? U-boot package does not update u-boot automatically.

It works with Armbian too. Just two years ago it was not in good condition

Solved.

Check this thread

Gnome uses Wayland and there some features don't work ... switch to X, where you will loose some functions, but remote desktop will work. FYI: https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277