Werner

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.

Image for H5 certainly won't work. Different SoC, even different architecture (32 vs 64 bit). You can give R1 image a try, doesn't look that much different besides the ugly yellow case. No idea how you built r1s images from Armbian since there is no dedicated config for this board in our build system. Maybe you used some sort of fork? Btw. if you don't mind please shorten your signature, like by removing the gaps between the lines. Thanks

tl;dr: Get a proper PSU.

AFAIK no need for something special. If there is no working bootloader on SPI available it should try to boot from eMMC and microSD.

https://docs.u-boot.org/en/latest/

We do not support 3rd party forks. Ask at the place where you got the image from.

armbian-install is meant to be used inside the running Armbian system from microSD card. It copies itself to NVMe or eMMC or whatever options are available and can be utilized. This tool does not work "offline". Anyway. I never did something like that by myself but maybe you find some hints when you google for keywords like "h616 fel sunxi-fel emmc". fel mode seems something like Rockchips maskrom to utilized the rkdevtool. Maybe Allwinner has something similar

Just like guests registered users can read any topic in any public forum.