nfslockd kernel module fails to load
Alexander Leidinger
Alexander at leidinger.net
Thu Apr 23 06:30:25 UTC 2020
Quoting Konstantin Belousov <kostikbel at gmail.com> (from Thu, 23 Apr
2020 09:19:08 +0300):
> On Thu, Apr 23, 2020 at 08:08:09AM +0200, Alexander Leidinger wrote:
>> Hi,
>>
>> link_elf_obj: symbol xdr_free undefined
>> linker_load_file: /boot/kernel/nfslockd.ko - unsupported file type
>> KLD nfsd.ko: depends on nfslockd - not available or version mismatch
>> linker_load_file: /boot/kernel/nfsd.ko - unsupported file type
>>
>> The xdr kernel module is loaded.
>
> The following should help.
> /* So that loader and kldload(2) can find us, wherever we are.. */
> +MODULE_DEPEND(nfslockd, xdr, 1, 1, 1);
> MODULE_DEPEND(nfslockd, krpc, 1, 1, 1);
I thought MODULE_DEPEND is only a way to tell the loader / kldload
that the other module is to be loaded in case it is not in the kernel
/ loaded already. Is this only a part of what it does and / or did
this change and now it is also needed so that a kernel module is able
to resolve the symbols? In my case the module is loaded already when I
try to load the nfslockd module.
Bye,
Alexander.
--
http://www.Leidinger.net Alexander at Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org netchild at FreeBSD.org : PGP 0x8F31830F9F2772BF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digitale PGP-Signatur
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20200423/7461c147/attachment.sig>
More information about the freebsd-current
mailing list