Re: nfssvc not available or version mismatch (nfsv4 client)

> >
> > kldload nfssvc && dmesg | tail -n 10 ?
> >
> 
> vm-salwerom% sudo kldload nfssvc
> kldload: can't load nfssvc: File exists
> 
> but:
> 
> vm-salwerom% sudo kldload nfssvc.ko
> vm-salwerom% dmesg | tail -n 10
> em0 at 194.29.146.128 server 194.29.146.27 server name amp2
> subnet mask 255.255.255.0 router 194.29.146.1 rootfs 194.29.146.3:/
> rootopts
> nolockd hostname vm-salwerom
> Adjusted interface em0
> SMP: AP CPU #1 Launched!
> Trying to mount root from nfs: []...
> NFS ROOT: 194.29.146.3:/
> KLD nfscommon.ko: depends on nfssvc - not available or version
> mismatch
> linker_load_file: Unsupported file type
> KLD nfscl.ko: depends on nfssvc - not available or version mismatch
> linker_load_file: Unsupported file type
> vm-salwerom%
> vm-salwerom%
> 
> 
> so, why if I want to load nfssvc I have to type it with the suffix?
> How can
> I tell nfsuserd and anfscbd to try to load it with suffix during
> system
> boot?
> 
I'm not very good at this stuff so others might need to chime in,
but it looks to me like some of your kernel modules are from different
builds.

I always:
# make KERNEL=<kernel_name> install
after doing a kernel build, which copies the kernel and all the modules
to /boot/<kernel_name>. I always use a <kernel_name> other than "kernel"
just in case it doesn't work, then you can move it over if is seems ok.

Both nfscl.ko and nfsd.ko specify nfssvc.ko as a module they depend on,
so they should be loaded automagically if all the correct versions are
in the /boot/<kernel_name> tree. (At least it works that way for me.)

rick