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 try in vain to install Virtual Box and its dependencies. The package "acpica" is my problem. When I try to execute its slackbuilds, I get this error message :
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Are you attempting to build the package on Slackware 64-bit 13.37? If so, note, in the README
Code:
VirtualBox Open Source Edition (OSE) is a general-purpose full
virtualizer for x86 hardware.
By default VirtualBox will be compiled with hardening enabled. That
means all binaries will be run suid root, which is the default
behaviour of upstream packages. However, you are still able
to disable this by passing HARDENING=no to the script.
You have to create a vboxusers group, e.g. "groupadd -g 215 vboxusers"
and make your user a member of that group.
To compile virtualbox without the Qt4 GUI pass QT4=no to the script.
To enable the webservice pass WEBSERVICE=yes to the script. This adds gsoap
to the list of required dependencies.
If you want to attach VirtualBox to a VDE network you will need vde2.
VirtualBox requires acpica, the jdk package from /extra, and the
virtualbox-kernel package is needed at runtime. See README.SLACKWARE
for some setup notes.
NOTE: This will not build on a stock x86_64 system.
If you did a full install of Slackware 64-bit 13.37, the acpica package should build without problems if the acpid package is installed (look at /var/log/packages/acpid-2.0.9-x86_64-1; it should be there). The SlackBuild for acpica does not require you to add the "ARCH" -- it's automatically detected.
It may be easier if you download the All distributions => AMD64 packages from http://www.virtualbox.org/wiki/Linux_Downloads -- the packages will be VirtualBox 4.0.8 (rather than 4.0.4 which did exhibit problems) and you simply
Code:
su - (or sudo)
sh VirtualBox-4.0.8-71778-Linux_amd64.run
to install it.
Be sure to also download Oracle_VM_VirtualBox_Extension_Pack-4.0.8-71778.vbox-extpack.
Those are your choices: install all the required packages from your Slackware distribution media or build and install all the required packages from SlackBuilds.org (including the kernel modifications you need to install) -- see http://slackbuilds.org/result/?searc...albox&sv=13.37; or download the current VirtualBox as above and install it.
1. You could use the SBo version, but it's for VirtualBox 4.0.4, plus you have to make a few tweaks to get it operational. It will not work with 4.0.8 due to build patch file incompatibility.
2. You could download and compile the source directly from Oracle, but installing it will take some effort to get it right. All lot more that using the SBo.
3. The best option (in my opinion). Simply install VirtualBox-4.0.8-71778-Linux_amd64.run. The installer does all of the work. Adds the vboxuser group, adds the rc.scripts to /etc/rc.d/, appends to rc.local and installs working udev rules. When the installer is finished the only things left to do are add your self to the vboxusers group, start "Virtual Machine" from the KDE menu (it's in System) and add the Extension Pack. Then you are all set to create your first VM.
Agree with tronayne.
3. The best option (in my opinion). Simply install VirtualBox-4.0.8-71778-Linux_amd64.run. The installer does all of the work. Adds the vboxuser group, adds the rc.scripts to /etc/rc.d/, appends to rc.local and installs working udev rules. When the installer is finished the only things left to do are add your self to the vboxusers group, start "Virtual Machine" from the KDE menu (it's in System) and add the Extension Pack. Then you are all set to create your first VM.
I agree with this option, but some notes
I don't think it's necessary to add your account to vboxusers. At least on my system, i don't use it and VBox is working just fine here
I don't think it's necessary to add your account to vboxusers. At least on my system, i don't use it and VBox is working just fine here
Agreed. I'm also running the Virtualbox package from Oracle and I did not need to set-up my account for vboxusers. Virtualbox is running just fine here as well.
You can also access some USB devices without the Extension Pack installed. My USB sticks work just fine with out the Extension Pack installed. That doesn't mean you shouldn't install it. USB support Installing VirtualBox and extension packs
Thanks, I used the Oracle installation script, and It's all right. I didn't create a vbox group, and it's working anyway. The abscence of "acpica" dependencie don't make problem.
I try to install virtualbox for Slackware 14.1 64bit and can't Building the VirtualBox kernel modules. Any help
ash-4.2# sh VirtualBox-4.0.8-71778-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation...........
VirtualBox Version 4.0.8 r71778 (2011-05-16T17:05:29Z) installer
Removing previous installation of VirtualBox 4.0.8 r71778 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules
Error! Bad return status for module build on kernel: 3.12.24 (x86_64)
Consult /var/lib/dkms/vboxhost/4.0.8/build/make.log for more information.
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ
You should not have necro'd a 5 year old thread just to post about your problem. You really should create a new topic and then follow the information in the error, namely:
Code:
Error! Bad return status for module build on kernel: 3.12.24 (x86_64)
Consult /var/lib/dkms/vboxhost/4.0.8/build/make.log for more information.
Look at that make.log and see if it provides you the reason why. If you can't figure it out, please start a new topic and post the resulting error that is in that file.
Also, since you are running 3.12.24, it is obvious you aren't running a completely stock Slackware. Please inform us if you didn't perform a full installation (what did you leave out) and any stock packages that might've been replaced. Also, did you use Pat's 3.12 kernel config in testing/ or did you cook up your own config?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.