how to add nfs module to kernel

Solom8

HI, i want to use Solus as thin\thick\diskless system because of boot speed.
Im testing this solution with LTSP, Solus should boot and get .img from nfs share.
But It drops me into emergency shell with an error
Failed to switch root
'uname -a' shows me latest Solus kernel, but i cannot find nfs module in /lib/modules/5.../kernel/fs/
also i have an error in emergency shell with 'mount -t nfs 1.2.3.4:/share /sysroot' -
unknown filesystem type nfs
I have added nfs into /etc/modules-load.d/nfs.conf , and after reboot lsmod shows me that nfs already loaded, but after network boot i have the same error. How i can add nfs module for earlier stage or enable in kernel by default, as SOlus dont have initramfs.

Here is part of rdsosreport.txt and grep nfs

last strings from rdsosreport.txt
path /sysroot does not seem to be an OS tree. os-release file is missing
--thats correct, sysroot is empty and there should be mount .img from nfs server.

kyrios

have you installed nfs-utils ?

Solom8

kyrios Yes!

ReillyBrogan I heard that Solus team doesn't want to support netboot due to some reasons.
So i need to download src and compile with enabled nfs? Is there some howto?

ReillyBrogan

That's because the nfs module is not included in the initrd. You will have to build and maintain your own kernel package here, booting Solus over the network is not a supported configuration.

WetGeek

Solom8 So i need to download src and compile with enabled nfs?

Do you know of another distribution that provides a kernal that includes it? It could be easier to change to that distro than to pursue this course. And that might eliminate the need to do all your own kernel builds and updates from now on.

Solom8

WetGeek I think all debian-based can deal with this, also as rhel. At least they have initramfs.

I have needful nfs modules on installed Solus, so just need somehow copy them into netboot live os before mounting nfs OR change nfs to existing module. FIrst one will be better, because i heard that cifs not so good for thick\thin clients as nfs/sshfs

Solom8

So ,i have added (i hope) kernel modules via copying and modrobe ,using ltsp.img layer.
re mkdir -p "$_DST_DIR/lib/modules/5.15.61-217.current/kernel/fs" test -f /etc/0 || re cp -a /etc/ltsp/kern_modules/* "$_DST_DIR/lib/modules/5.15.61-217.current/kernel/fs/" re modprobe nfsd re modprobe nfs

something changed in boot process ))

thats what i have now =>
/lib/dracut-lib.sh no such file or directory with loop and i cannot enter emergency shell =(

Video of boot process
https://transfer.sh/AFORM4/Screen%20Recording%202022-08-23%20at%2000.14.18.mov

ReillyBrogan

Unlike most distribution Solus builds the initrd during packaging of the kernel package. So the correct way to do this would be to setup for building packages, clone the linux-current package (git clone https://dev.getsol.us/source/linux-current.git), and then change this line in the package.yml

--kver $kversion --add "bash systemd lvm dm rescue" \

--kver $kversion --add "bash systemd lvm nfs dm rescue" \

This will configure dracut to include the nfs module which should automatically add the correct kernel modules to the initrd. Note that if you receive errors about missing binaries you will need to find out what which package stores the binary mentioned in the error and add it to the builddeps section.

FYI this is a completely unsupported use-case for Solus. I'm not even sure the instructions I've given you will be sufficient, they are just my best guess as to what you need to do. Note that even if you get this working that you will need to re-do it every time Solus updates the kernel.