Werner

moved

I'd do the following: Boot any image that works for your and check if /dev/mtd0 is present. Then simply overwrite it with dd if=/dev/zero of=/dev/mtd0. May take a few minutes. This type of memory is rather slow at writing.

Wipe SPI/eMMC before trying to boot vendor/legacy/3rd party OS from microsd again.

https://docs.armbian.com/Developer-Guide_Build-Preparation/

We cannot afford to provide pre-made images in every kernel-userspace combination for every board. The amount of resources necessary could be just insane. However that is what the build framework is made for so you can choose exactly what you want and build it by yourself. https://github.com/armbian/build

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

6.10 is, as the name implies, bleeding edge, so do not expect stuff to work. Mainline support for rk3588 is still in development. In theory though HDMI should work already, however might not have been tested on this device yet and there are caveats. Anyway if you prefer a working system, get an image with vendor 6.1.y kernel. Regarding the ssh stuff I think @Alessandro Lannocca did some work on SSH, either you grabbed an image where fixes were ongoing or you found another bug that needs attention.

Might be a known similar issue where when using armbian-install on OPi5 the contents of /boot is not copied to the nvme and therefore booting fails. However copying everything manually and adjusting the blkid it works just fine.

https://github.com/armbian/build/pull/6771

In theory everyone can create fake Armbian images since it is open source. This is why authenticity is important. Debug boot issues: https://debug.armbian.de

Those images are fake https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity

You can use the build framework to build images for any board with any kernel and any desktop you want. https://github.com/armbian/build/

fixed

Which is exactly the same as armbian-config but with code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } sed 's/armbian/orangepi/g'

https://docs.armbian.com/Developer-Guide_Welcome/#command-line-syntax-has-changed This also kind of applies here: https://zuckerbude.org/armbian-using-kernel-config/

Hi, Armbian by itself does not accept new boards without funding/agreement. However anybody can contribute code via pull request and add community support for it. https://docs.armbian.com/Process_Contribute/

moved. question is too unspecified.

do-release-upgrade most likely will not allow you to update to Noble until this date. None. Lunar is EOL, repository has been removed.

Make sure to - write SPI during the mentioned armbian-install process - that /boot directory has been populated on the NVMe. If not mount and copy files from sd manually there.

Install matching rootfs package for your hw, whatever it might be.

Yeah cpufrequtils is deprecated. The way to go today seem to use linux-cpupower. No idea though how well this works on SBCs.

If you want to upgrade the userspace flavor on top (like Jammy to Noble for example) it is indeed recommended to start from scratch. If you want to upgrade the Armbian core components like firmware, kernel and boot-loader, these upgrades are shipped as regular apt package.

For Armbian updates regular code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt update && apt upgrade will be sufficient. If you however want to change your userspace (like Jammy to Noble) this is out of scope of Armbian and upstream tools (like do-release-upgrade in case of Ubuntu) have to be used. Armbian firmware and userspace are two pair of shoes. Armbian cannot handle userspace upgrades by itself simply due to lacking of both human and financial resources for development and testing lots of various scenarios. This is also the reason why doing this is not recommended and therefore entirely unsupported by us.

mainline support in 6.8 is to be considered experimental at most. Breaking is likely since it is bleeding edge. Feel free to use an image from earlier release. I hope at some point things get rebased on 6.10-rc where lots of new stuff hit mainline.

Maybe. However nothing we could do anything about.