Werner

That wont work in this special case. Only for kernel sources that are patches by upstream. On sunxi-legacy however from a specific point Armbian had to print upstream patches by themselves. Sounds complicated but for you a rather easy fix. Check https://github.com/armbian/build/tree/master/patch/kernel/sunxi-legacy and remove all upstream patches above 5.4.45 Btw as branch you need to use "legacy" instead of "current" since the branches have been cycled a few days ago. current would give you 5.7 kernel.

Not sure if I get that right. You are using QEMU to kind of nativly build armbian on arm?

You're welcome! Glad to hear you could make progess. If you come across stuff that can be enhanced or patched and you would like to share with the community please do so. Armbian heavily relying on community contributions.

https://armbian.atlassian.net/projects/AR/issues/?filter=allissues&= https://github.com/armbian/build/issues Feel free to dig through some open issues and address some

Thx for the PR. You can also things like blacklisting the wifi module, using iwconfig wlan0 power off ...

Yeah I know, saw the YT videos Unfortunately there is not much documentation in that case. It is quite hard to keep track what are current issues, what has been solved, what is new and everything across literaly hundred boards... Anyway what might be interesting for you is to check JIRA for open threads: https://armbian.atlassian.net/projects/AR/issues/ I could have mentioned that before. Support terms are stated here:https://github.com/armbian/build#support And no, I am no maintainer or developer. I am just a random guy that spends (sometimes too much) time in the forums and help others and collect information that might be useful for actual contributors. The issue in general is that the team behind Armbian is way too small for the amount of work and can barely catch up with everything. This of course has some downsides and relying on the community to provide p2p support.

Since both Bionic ans Focal flavor of Armbian sharing the very same kernel package this could be an upstream issue. I know @NicoD has n M4V2 as well, maybe he finds some time to do some tests to confirm.

https://duckduckgo.com/?q=root+console+auto+login+bionic&t=ffab&ia=web 2nd result and don't forget to check with https://www.armbian.com/donate/ for the wasted time

cd ~ mkdir -p .ssh cd .ssh && nano authorized_keys Put a key in there like ssh-rsa AAAAB3NzaC1yc2EAAAABJQAABAEAg2gnuBk/z/8aG333k1bQV8a08LNzjyrUos8/eftKMxCRLpvYOlrkkLxffd7cNJUCHOP9flRx8qlyMbrkFLqBvVXmnRcTJiGZujFGO6NIkcploGCM7ai9mVECrjOUfSzl7Psdq4F+XXYyXeJIgPuCeFqtKU53wGEqgeO+vWb7ZgssgFBxc6iPudHiEpvnPAUN32YDoEORCYEwvM59+p58mRkooyYsgiej4D8Jibh+rCncARkfl48tilTkwH4qB2NbVHvqexUO7A9Wk6RYG2az99cenc24HWihnhLDjA4N4LP3Xfm57wYzNZZ1MPDYfQYgtK5/8MJCx1MQOTLb/lpjvNhXF+XLSontGb2VZUW8ZRSRYlWxwvy/JDPoPlcpQ/itbHdeqkekqpRoPvCZBLZy9odqDdOoLx090xFE+vUGRrNlhIEub+6KhCj11g+bhMyoO2QV/i4P7ff+BvMOmiRRda1NdS+7KVZeR6HiABS2gbgPmaNkA9+FVSVhJa/ShKSwOeDZlQkM0CQei6COo1tTKHt57/kXqPSP9VYIlZknDdFYEwdpC9tJi+hN6Qn+Qk6IcBoL1PXVVNmfwRMxAJaHa0PVa1X/ivQjLqCCi5YKx4tziDbFXNNPVxJ8h14qoTP9WQa3Aq2zV3JQKUktEbjCA+ibotoP1QtzEpPHCd7TRwCMm3Awhcw+fRzQ04aXCasN0nqmk1zZ9Vx21jwUpg5mTBdAKn5ZEVCIPOUs7D4GRPcIIPATSxrIJh302FSiHAO+8RH5X3J/gYWCQzT76P6C5G65rkx/a2PXCPYqR92BeFXBmxM/OQzlMLuYFQJg5nkvGdiQDjASzDV0WfSPV+QU1bxZzWsBXxnNBAi7xnVDRnJwgUknMTW5VeFnEUqazU5+8njHlq2ArhCYrsn3c4rJtlWFLK95PkUlg2+NxqL3gJBS/8luzJeLzpztAIlXWi2LOXRwERedaDxauht9oGQUIM+jIeWUn55qw2SC/C24S9BSTjBAIQXHn9d/sgIXRQm/7IChxr2PnIXE0JjSfqg4a1UC8C5rfnARIWEJ0siUDEmOq0Ocvb+GzHknSUbUzg8sUkyVvDfpNbNQ2RygRJs/Of6iYJdNily8X1buNuDe7UAsBhXAGprC9xUVxCa7vIbepz9Qhq24NsIxXRBNM04wn/knPvma3zEG58JfdPbP0cuQLpEznGo3NqLRviB1/Booal1b/X1S17f/rzT/acaGYHqqI73YdZ7DBXl7t6FZ0d75VEAG2gwB6RN87lgV/1ghW4KuK7QpvDnB7A46Kj3CXSQrg14bY6Oc0LO15UsG5kYgBRLk3S5Xqw1by4Pcv2uQhpglc6Vs7FmDlb1JmcN7eQ== rsa-key-20200720 Selected the private key in putty and worked flawless. Put the private key here as well for you to test. No password. test.ppk

About a year ago this was correct. All 3.x kernels have been dropped due to lack of upstream support.

Did you literally upgrade to focal (do-release-update) or started with a new image?

Actually no, you do not have to. Though the performance seems slightly better with kernel >=5.6.x

OrangePi One with 5.7.x as current: http://ix.io/2s2m Booting, Network is working, cpufreq is working, nothing else tested OrangePi One Plus with 5.7.x as current: http://ix.io/2rsX Booting, Network is working, HDMI is working, cpufreq is broken, nothing else tested OrangePi Zero with 5.7.x as current: http://ix.io/2s2p Booting, Network is working, WiFi seems to work (did not test connecting it somewhere), cpufreq is working, noting else tested

Hm. Maybe it is a emergency shutdown due to thermal issues? Did you check the temperature under load?

And maybe switched the kernel?

As suggested did you check journalctl -xe for details?

Which exact image did you use? My OPi Zero is just fine:http://ix.io/2rZ7

Where did you get the log from? Do you have a serial console on it?

Well if you already reached out for the search function there is nothing much to add here since the topic lacks of further fundamental information like armbianmonitor -u, configs, error messages....

Please check https://docs.armbian.com/User-Guide_Basic-Troubleshooting/ Did this board run with Armbian before? If so which version? Do you have a chance to put a serial console on it to see whats going on in there?

You should get a proper one. Best debug tool for SBCs. OPI4 is built around the RK3399 SoC but since youo state it does not boot at all it kind a finds here too.

rien ne va plus. Code freeze day

No worries. Guess the information collection needs to be enhanced there... (feel free to contribute ) Not sure if I got that right. It does work in 4.13.x but also does in legacy branch 4.19.x?

Main language here is English. If you are unable to write so please use a translator at least. Nobody will care about your post otherwise.

Not really. That overlay stuff is beyond my skills