Werner

Interesting. This needs to be investigated. https://armbian.atlassian.net/browse/AR-340

Once again in this particular case defining a specific branch won't work since sunxi relying on 3rd party sources. In your particular case here: https://github.com/megous/linux/tree/orange-pi-5.4 You can find these also when you start digging through the configs for your boards and their matching board families. Back to the sources: Megi does not add tags and also maintains a kernel version only to a certain level and mostly works on the newest available sources. It is up to us as we use these sources to keep them halfway up to date if possible and we do that using our patches. The location you can find in my previous post. There is no general way to get specific kernel versions for every single board. The wide variety of boards makes that impossible.

The only thing that catched my attention by digging through the logs is that at the first boot wifi was there as wlan0. Also firmware was loaded: [ 7.465721] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4356/2 wl0: May 14 2014 19:51:52 version 7.35.17 (r477908) FWID 01-2ed3ee81 That particular line is missing in all the other boot logs where wlan0 is missing too. So maybe the firmware is missing. Check if the armbian-firmware-full (was it I think) package is installed and maybe do a reinstall.

Do you have an armbianmonitor -u output for us? Did you modify the device tree?

I don't know. Maybe, maybe not. I neither have this board nor access to a similar one to test atm. Dealing with SBCs often is try'n'error. That is the usual business....

As far from what I see it is not software rendered. That would be LLVM. What you can try is to install mesa from scratch or use oibaf ppa (I had more success on H6 with 1st method though) to get more up to date mesa binaries and/or install a more recent kernel. You can compile a 5.7 kernel package for sunxi64 using the build script: github.com/armbian/build/ or check nightly builds for trunk kernel packages.

Should be possible. I want to mention two things here: First: https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script This allows do add customizations to an image right before it is being packed into an img file. And 2nd have a look at:

Enjoy yourself

That could be an issue. This kind of upgrade is neither tested nor supported. If you have a chance try with a fresh image. And always handy to have: armbianmonitor -u

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?