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.
I downloaded the link for "all distributions". Have to be administrator though. Then, I restarted the computer (I guess I didn't really have to) in order for the kernel module to find its place. Then it all worked well. It installs all the files in /opt (except the module), so I didn't worry about it placing some odd file where I didn't want it. I don't have it packaged though, which of course would be preferred.
I downloaded the link for "all distributions". Have to be administrator though. Then, I restarted the computer (I guess I didn't really have to) in order for the kernel module to find its place. Then it all worked well. It installs all the files in /opt (except the module), so I didn't worry about it placing some odd file where I didn't want it. I don't have it packaged though, which of course would be preferred.
i found some tutorials on the net. it said something like dependency issues right now im downloading the libraries that the tutorial said.. or do i just install the VirtualBox-xxx-xxxxx-Linux_xxx.run file and it would work right out of the box?
The binary installer didn't work on my 64-bit Slackware 13.
Code:
Building the VirtualBox vboxdrv kernel module
Failed to build the vboxdrv kernel module.
Please check the log file /var/log/vbox-install.log for more information.
VirtualBox has been installed successfully, but the kernel module could not
be built. When you have fixed the problems preventing this, execute
/etc/init.d/vboxdrv setup
as administrator to build it.
And the contents of the aforementioned log:
Code:
VirtualBox 3.1.4 r57640 installer, built 2010-02-12T19:37:27Z.
Testing system setup...
System setup appears correct.
Installing VirtualBox to /opt/VirtualBox
Output from the module build process (the Linux kernel build system) follows:
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.29.6/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
Makefile:529: /usr/src/linux-2.6.29.6/arch/amd64/Makefile: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-2.6.29.6/arch/amd64/Makefile'. Stop.
make: *** [vboxdrv] Error 2
End of the output from the Linux kernel build system.
Installation successful
EDIT: I guess I should say it didn't work as expected. I worked around it by doing a make; make install in /opt/VirtualBox/src.
Under /usr/src/linux/arch you probably don't have an "amd64" folder. Make a symlink with the name amd64 to the x86_64 or x86 directory, or possibly patch the Makefile in question.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.