It may be better to do this with an overlay, as a kernel update will wipe out any changes you make. If you're not seeing anything on any of the I2C buses, I'd first check your wiring. You should have 4 wires, SCL, SDA, GND, and either +3.3V or +5V (depending). Next, I'd check for similar boards to your M5. A quick search suggests it's an Amlogic S905X3, which is the same Meson SM1 CPU as the ODroid C4. And there's a pair of ODroid C4's overlays to enable I2C, and they're doing more than setting the status to "okay". May be worth a try? - meson-sm1-odroid-c4-i2c0.dtbo - meson-sm1-odroid-c4-i2c1.dtbo Failing that, I'd check to see if there's anything useful in the Banana Pi forums or documentation on how to enable those I2C buses. I'm afraid some of the Amlogic documentation may be somewhat limited.

If you want to use network manager you have to make sure systemd is not overriding your configs, ie disable relevant systemd services. To me, it sounds easier to just use what is installed default, in this case systemd and use networkctl to interact. But it should be irrelevant. If you configure your dhcp server and dns server correctly, both systemd and network manager should pick up correct config in default config state so you should not even have to interact with either of them. (I started assuming you are using a minimal image, therefore systemd as default. You haven't disclosed what version you use, just something 26.3)

NetworkManager is how I have been trying of configure end0 but it won't run by itself, ONLY when armbian-config runs it as a client. IDK if I can copy/paste its show me output.

Either the config on the device is wrong, there is supposed to be a dns ON the device or the dhcp server is handing out wrong dns to the device. Not on every specific device if there is a local dns server available on the network. Then it's normally done on the local dns itself by first checking local configs (like /etc/hosts) and if not available, resolve using online dns servers and then send the response to the device. And the dhcp server is obv configured to point to the local dns server. That way the configs gets propagated via the dhcp lease to all devices on the network. Edit As far as I know, network manager is default on armbian (correct me if I'm wrong) and that should have edited your /etc/resolv.conf. So since it's not, you have made changes outside of default config somehow. Could be that the specific release and device you use does not utilize network manager. But since you have not disclosed that info, hard to know. But it looks like you use systemd-resolved so you should check how that works. Edit2 I was wrong about network manager, see https://docs.armbian.com/User-Guide_Networking/

gene@amanda:~$ resolvectl status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (end0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 192.168.71.0 DNS Servers: 192.168.71.0