[SOLVED]mkinitcpio cannot enable netconf

Quadro · 2022-08-08 13:23:27

Hello everybody!
I am trying to set up remote unlocking LUKS root partition (with dropbear) and faced an issue I cannot find the solution for.

What is done:
1) /boot is ordinary, / is encrypted
2)

 HOOKS=(base systemd autodetect keyboard sd-vconsole modconf block netconf dropbear encryptssh sd-encrypt filesystems fsck)

3) ip=:::::ens33:dhcp in grub.cfg
4) while making

mkinitcpio -p linux

I got the following

Created symlink /tmp/mkinitcpio.Xdc5gE/root/etc/systemd/system/dbus-org.freedesktop.network1.service → /usr/local/lib/systemd/system/systemd-networkd.service.
Created symlink /tmp/mkinitcpio.Xdc5gE/root/etc/systemd/system/multi-user.target.wants/systemd-networkd.service → /usr/local/lib/systemd/system/systemd-networkd.service.
Unit /tmp/mkinitcpio.Xdc5gE/root/usr/local/lib/systemd/system/systemd-networkd.service is added as a dependency to a non-existent unit multi-user.target.
Created symlink /tmp/mkinitcpio.Xdc5gE/root/etc/systemd/system/sockets.target.wants/systemd-networkd.socket → /usr/local/lib/systemd/system/systemd-networkd.socket.
Failed to enable auxiliary unit systemd-network-generator.service, ignoring.
Failed to enable auxiliary unit systemd-networkd-wait-online.service, ignoring.
Systemd is enabled, but there are no .initramfs files under /etc/systemd/network; exit

therefore network doesnt work when it is time to unlock encrypted root partition, as I am told

[FAILED] Failed to start Network Configuration.

if I switch to udev, then process doesnt even go to the phase of asking the password and kicks me into rootfs

Could anybody give me a hint what and why it does happen?

Thanks in advance.

Last edited by Quadro (2022-08-10 13:44:38)

seth · 2022-08-08 22:19:36

ip=:::::ens33:dhcp in grub.cfg

Did you try

ip=:::::eth0:dhcp

?

https://wiki.archlinux.org/title/Dm-crypt/Specialties#Remote_unlocking_of_the_root_(or_other)_partition wrote:

By default, Predictable Network Interface Names are activated and change the kernel device name during late boot. Use dmesg and look what your Network kernel module does to find the original name (e.g. eth0)

If you feel better about it and don't have multiple wired or wifi NICs, there's no benefit in using that itfp, https://wiki.archlinux.org/title/Networ … face_names

Quadro · 2022-08-10 13:43:28

seth wrote:

ip=:::::ens33:dhcp in grub.cfg
Did you try
ip=:::::eth0:dhcp
?
https://wiki.archlinux.org/title/Dm-crypt/Specialties#Remote_unlocking_of_the_root_(or_other)_partition wrote:
By default, Predictable Network Interface Names are activated and change the kernel device name during late boot. Use dmesg and look what your Network kernel module does to find the original name (e.g. eth0)
If you feel better about it and don't have multiple wired or wifi NICs, there's no benefit in using that itfp, https://wiki.archlinux.org/title/Networ … face_names

You are absolutely right! eth0 is hardcoded so it has nothing similar to real name of my network interface. The problem is solved!

Slithery · 2022-08-10 13:45:21

Please remember to mark the thread as [SOLVED].
CoC - How to post

Arch Linux

#1 2022-08-08 13:23:27

[SOLVED]mkinitcpio cannot enable netconf

#2 2022-08-08 22:19:36

Re: [SOLVED]mkinitcpio cannot enable netconf

#3 2022-08-10 13:43:28

Re: [SOLVED]mkinitcpio cannot enable netconf

#4 2022-08-10 13:45:21

Re: [SOLVED]mkinitcpio cannot enable netconf

Board footer