ports/151603: Self-built virtualbox-ose-kmod vboxnetflt.ko kernel module fails to load with "link_elf: symbol RTR0Init undefined" message
Tadaaki Nagao
abtk at shitamachi.org
Tue Nov 16 18:00:24 UTC 2010
The following reply was made to PR ports/151603; it has been noted by GNATS.
From: Tadaaki Nagao <abtk at shitamachi.org>
To: ggg_mail at inbox.ru
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: ports/151603: Self-built virtualbox-ose-kmod vboxnetflt.ko
kernel module fails to load with "link_elf: symbol RTR0Init undefined"
message
Date: Wed, 17 Nov 2010 02:58:19 +0900 (JST)
Hi,
In "ports/151603: Self-built virtualbox-ose-kmod vboxnetflt.ko kernel module fails to load with "link_elf: symbol RTR0Init undefined" message",
Grigory Rechistov <ggg_mail at inbox.ru> wrote:
> I found that on my system certain Virtualbox kernel modules fail to
> load after they are build from ports system as opposed to ones
> installed from packages. For instance, I decided to upgrade
> virtualbox-3.2.6 to virtualbox-3.2.8. THe former was from packages,
> the new version was build from ports with portupgrade.
>
> But when I try to load new modules I am unsuccessfull:
> # kldload vboxdrv // this works OK
>
> #kldload vboxnetflt // returns "No such file or directory"
>
> Additionally I get "link_elf: symbol RTR0Init undefined" on 1st console and in dmesg.
I encountered the same issue a few months ago and have found that if I
uninstall devel/binutils or tweak my $PATH so that the base system's
binutils (/usr/bin/ld, etc.) can be found first, the kernel modules
from virtualbox-ose-kmod build and load successfully.
If your system also has devel/binutils installed, try moving
/usr/local/bin in your PATH environment variable to somewhere after
/usr/bin and rebuild and reinstall virtualbox-ose-kmod.
> I also noted that certain other ports that require kernel modules
> (e.g. cuse4bsd and webcamd) fail to load the module and work if they
> are built from sources not acquired from packages.
Perhaps the same tweak also works for them. Give it a try and see.
Hope this helps.
--
Tadaaki Nagao <abtk at shitamachi.org>
More information about the freebsd-ports-bugs
mailing list