Werner

Seems like all patches were adopted. Just make sure to use edge branch. Alternatively you can use legacy which will use old outdated vendor bsp for u-boot and kernel.

Compiling firmware for arm devices is unfortunately a lot of more and quite a few hacks are necessary to get everything in order so that it boots or works to say. That is why armbian was created to be do all this stuff for the user. It is also not only the kernel that need to have drivers for all the functions but also u-boot. No idea what sources Zero2 images are currently built of and (if not directly from Andre's branch) up to which point his patches were adopted. Like many other boards Zero2 has no dedicated developer that takes care of it. Also if maintainer is not much active it's current status remains unknown.

Topic closed on authors wish.

No Lite2 has H6 SoC while Zero2 has the newer H616. Probably nothing spectacular besides no boot. https://docs.armbian.com/User-Guide_FAQ/#why-i-cannot-simply-shove-a-random-image-into-my-board-to-work-like-on-my-pc

moved

Try 115200

Probably because nobody considered yet adding it because there is a need for it Feel free to do so by providing PR here: https://github.com/armbian/firmware/

If you search you find threads like this: This topic is about feedback to Nico's video rather than support for the device.

Simply use armbian-config to freeze all packages involved

https://fi.mirror.armbian.de/archive/nanopi-r2s/archive/ Depends on how old you expected it...

From what I've read regarding this it seems safe if you freeze firmware packages beforehand. Those dist-upgrades are neither tested nor supported simply because Armbian does not have the resources to test those. Therefore if something goes wrong you are on your own. In any case create a backup of your system beforehand.

Fixed. Thx.

First of all thank you for taking the time to check for common pitfalls beforehand. There aren't many people doing that unfortunately before complaining. LXC or similar containerized/PVM solution besides docker will not work. Proper HVM like KVM, VirtualBox and so on are perfectly fine. Virtualization type: microsoft That was hypervisor I assume? s5p6818 Oh boy, that thing did not get attention for quite a while I think. Well it's csc and if nobody from the community steps up to take care it will compost over time 😄 Anyway there are further logs in debug since raw output log does not go into detail. Check compilation log and other for deeper insights.

Of course it is but going this way gives first clues where to start looking

Odd. Iptables is enabled in kernel config. Can you check with a fresh image? https://www.armbian.com/download/ Also maybe check /lib/modules/5.10.123-meson64/kernel/net/ipv4/netfilter/ if there are other modules available or all just missing.

Did some cleanup here. Might be slightly off-topic but I won't serve anything via WiFi lol.

Maybe you could do a comparison between Armbian and Kali dtb by chance? Would be neat to know if we miss something.

@NicoD @lanefu don't you have pbp for a quick test?

You can use the build framework to create an image containing software you like: github.com/armbian/build

@dev001

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

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

"supported" is a relative term. There is no SoC that has 100% of HW functions working stable. As a compromise between most recent and most stuff working I'd suggest something built around the RK3399. Newer but less stable/stuff running is any RK35xx chip.

https://tvheadend.org/projects/tvheadend/wiki/Faq#Help-I-cant-login-to-the-web-user-interface

Feel free to provide PR to enable those module across all kernel configs.