Werner

Probably Armbian also needs a dedicated image for that or some dirty hackjob to allow both variants to boot. Anyway I don't think somebody will waste time on this task...

Which branch did you try? vendor? edge? legacy?

Correct. Glad you made a backup beforehand.

You can put the microsd in your computer and check a few things like is /boot populated? does the UUID of the root partition match in armbianEnv.txt and /etc/fstab?

Both 5.10 and 6.1 are vendor bsp and have nothing in common with collabora/mainline. Their hw support status should be more or less identical. mainline is 6.8 or 6.9-rc

Hi, not sure if module blacklisting affects initramfs creation, however it should prevent the module being loaded at boot time. Did you check if this works as expected?

Hey, if this works for you just fine then there is not much to worry about. Consider either freezing firmware via armbian-config or create a backup of your OS before doing major updates like kernel since those nightly images feed themselves from the beta repository. Anyway you are free to build your own image using the build framework. Check the documentation, for standard images there isn't much to it. https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://docs.armbian.com/Developer-Guide_Welcome/ In terms of kernel choice there isn't a perfect solution yet. Both legacy and vendor are, as their names imply, aged vendor bsp kernels which support most board functions but on the downside won't receive much attention in future. On the other hand there is edge which follows mainline as close as possible but is under heavy development to add missing board features and until completion, if this state is ever reached anyways, will take years at least. Basic functionality is there and its mostly fine for server tasks.

Never heard of. Therefore probably no ready-made images exists. https://docs.armbian.com/Process_Contribute/ https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

Set verbosity to 7 in armbianEnv.txt

debug.armbian.de

https://www.sparkfun.com/datasheets/IC/cp2102.pdf https://x.na4.eu/KOTu3/ZAfupUHU45.png

Press X for 'doubt'. The CP2102 cannot handle 1.5Mbaud

Well you could try to write a dtb overlay to add higher clock notes but in most cases it is simply not worth the time since they performance "gain" is negligible in comparison to both the increased power draw and the high chance to fry the SoC while attempting this. Not worth taking the risk.

Tried something mentioned here? https://www.google.com/search?q=debian+autologin

Sure but do not expect this to happen (soon) without funding.

May not even work yet. mainline is still bleeding edge and is missing features. If you need full functionality keep using legacy kernel.

Actually there is. ### meminfo: MemTotal: 949752 kB And after: ### meminfo: MemTotal: 882904 kB Maybe uboot issue with memory detection?

That decision is up to you. Give both options a try and decide for yourself. As for me I'd always prefer some free operation system over proprietary stuff unless if have no other choice.

As long as the CPU is 64 bit it should work just fine

Armbian is very limited in both human and financial resources. We cannot afford either supporting software that is EOL upstream for one and a half years now or storing hundreds of thousands of old packages. Don't get me wrong. It would be nice to have stuff kept around and supported way longer. But who should take care and pay for it? docs are unfortunately often outdated, last but not least because of the reasons mentioned above. It is already difficult to keep up with ongoing development and changes and documentation takes time as well. Feel free to help improving the situation and get involved.

Check archive. If it is not there it is gone.

Yes, that will work unless there is some special weirdness in the R1S-H3 that needs custom drivers...which I doubt for now

Yes. However there are various SoC manufacturs for arm64 SoCs like Allwinner, Rockchip, Amlogic and so on and they require custom patching for often both uboot and kernel. So while saying the device tree is indeed the biggest difference it does not boil down to just that.