SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyone else running 6.1.34 in current also have problems loading a VM?
I am getting the following error
Code:
Failed to load R0 module /usr/lib64/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND).
Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci' (VERR_SYMBOL_NOT_FOUND).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Did you build from source? And if so did you have any warnings when building the VirtualBox-kernel portion? Are you using kernel 5.17.7?
I did not build from source, used the installer. I noted above I am on the the latest -current, so yes kernel 5.17.7.
I always remove and install VirtualBox before and after each kernel upgrade. There was no issues in building the kernel using the VirtualBox installer.
Would 6.1.35 fix this problem or is also in that release as well?
It was fixed in the binary release of 6.1.34 after the issue was found so it would stand to reason that it is also fixed in the 6.1.35 testbuild. Although I can't confirm that.
Can't speak to what's needed for the binary installer though.
I'm having problems building with that script. I'm getting the following error.
Code:
C VBox-xpcom-nspr - {C}/src/libs/xpcom18a4/nsprpub/pr/src/io/prfdcach.c
javac vboxjxpcom.jar - jxpcomgen.list
warning: [options] bootstrap class path not set in conjunction with -source 5
error: Source option 5 is no longer supported. Use 7 or later.
error: Target option 5 is no longer supported. Use 7 or later.
kmk: *** [/tmp/VirtualBox-6.1.34/src/libs/xpcom18a4/java/Makefile.kmk:212: /tmp/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxJXpcom-inst-jar/vboxjxpcom.jar] Error 2
kmk: *** Waiting for unfinished jobs....
C VBox-xpcom-nspr - {C}/src/libs/xpcom18a4/nsprpub/pr/src/io/prmwait.c
C VBox-xpcom-nspr - {C}/src/libs/xpcom18a4/nsprpub/pr/src/io/priometh.c
CXX VBoxOGL2D - {C}/src/VBox/Frontends/VirtualBox/src/VBoxGLSupportInfo.cpp
AR RuntimeR3
kmk: *** Exiting with status 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
