You are not logged in.
I am hitting multiple back to back walls and not really sure how to fix them. I am attempting to get a functioning pxe booting linux on an old micro pc to power a pick and place machine.
To start I followed the guide at https://wiki.archlinux.org/title/Diskle … stallation but it has its problems and im not even sure why. To start the command add_module nfsv3? within /usr/lib/initcpio/install/net and the copied usr/lib/initcpio/install/netnfs4 seems to throw an error during initrid generation, see below. The end result is that nfs is included but not nfsv3 or nfsv4 unless you specifically add them to modules like in the guide.
/usr/lib/initcpio/functions: line 704: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 704: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 739: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 739: _addedmodules[]: bad array subscriptI found another with similar problems on unix stackexchange which list some other issues https://unix.stackexchange.com/question … tart-switc
Doing some more debugging using ip a I realized that the realtek cards modules were not included in the initramfs and that could be the source of my issues right? so I added it with MODULES=(r8169) and rebooted... no luck.
Following more debugging steps I made a full initrid image by removing auto detect and... nothing. I could see eth0 and if I used ip commands to set a default route and ip then I could fully boot, but could not get it to go in one shot. Checking the hook scripts ran for net and netnfs4 I realized it calls the ipconfig command to setup the network based on the ip= parameter. So I tried to run it myself after it failed to boot and get ipconfig: no devices to configure. If I run ip a I can clearly see eth0 and lo so I decide to try a different method.
searching around more I found someone else who added systemd-networkd to initrid for remote rebooting a encrypted system at https://tavianator.com/2022/remote_reboots.html, so why not try to do the same here. I added their lines to netnfs4 to include systemd-networkd and made a catch all network script to DHCP on any interface. Reboot to fail, systemd-networkd is there and status shows it ran and recognized the interface but didn't set any ip addresses or even run DHCP. I then make a network file for a static IP and same effect after a reboot, systemd-network runs, shows no error, recognizes the interface, doesn't set the ip.
So now I am at a loss as to what I am doing wrong and why seemingly nothing outside of the ip command can set an address to finish the nfs boot.
EDIT: As further debugging and to make sure I am not insane I added the required ip commands to the netnfs4 hook and similarly no errors but also no ip set.
Last edited by Whinis (2026-06-01 02:14:39)
Offline