Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Odroid M1 can't enable eth0 with systemd-networkd on boot

Featured Replies

Hi, 

 

i have a Problem, where the Network is not coming up.

What i have done:

  • Installed Arbmian Bullseye CLI on SD Card
  • Booted it on Odroid M1, update and updgrade system - Reboot
  • Until then, the NetworkManager is active and works
  • Installed OMV through armbian-config
    • OMV kills all NetworkManager stuff, and enables systemd-networkd
    • and it does that as i can see correct, with netplan etc...
  • After reboot, the boot hangs 2 Minutes in "A start job is running for Wait for Network to be Configured" and finally boots - without IP

 

Boot finished - login and try to find the error:

  • networkctl shows eth0 is off and unmanaged
  • systemctl status systemd-networkd has no errors and logs:
    • Starting Network Service
    • Enumeration Complete
    • Started Network Service
  • systemctl status systemd-udevd is active and running, but got errors:
    • Starting Rule-Based Manager for Device Events and Files
    • Started Rule-Bas...
    • Using default interface naming scheme 'v247'
    • eht0: Failed to query device driver: Device or resource busy

 

Also, my netplan configuration searches the eth0 by MACaddress:

 

cat /etc/netplan/20-openmediavault-eth0.yaml

network:
  ethernets:
    eth0:
      match:
        macaddress: "some macadress"
      accept-ra: true
      dhcp4: true
      dhcp6: true

 

If i remove the match by macaddress or change it to name: eth0, the reboot works and it gets an IP and network is running.

So i observed the macaddress, and networkctl status eth0 shows another macaddress each reboot.

Why?

 

I can't help myself, after 2 Days of searching the whole internet, nothing seems to be close to my problem.

 

Someone ideas?

Greetings

 

Edited by chamabreu
Add information for macadress matching

22 minutes ago, chamabreu said:

OMV kills all NetworkManager stuff, and enables systemd-networkd

If the system was running flawless before installing OMV and does not after I suggest to blame them 😄.

What armbian-config more or less does only is downloading the omv install script and execute it.

https://github.com/armbian/config/blob/eebfc58c140a34d6e28db5ecbc5faba6b8432ca4/debian-software#L559 ff.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.