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.
slackuser@slackmachine:~$ mount
/dev/sda2 on / type jfs (rw,discard)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type jfs (rw,discard)
/dev/sdb1 on /home type jfs (rw)
gvfsd-fuse on /home/slackuser/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=slackuser)
slackuser@slackmachine:~$
You've plenty of space available, so, I was wrong about the cause of the error message.
I doubt about that, but maybe there is something wrong with jfs ...
Otherwise, try to run /sbin/rcvboxdrv setup multiple times and check if you get always the same error (ie. No such file or directory) in /var/log/vbox-install.log.
slackuser@slackmachine:~$ mount
/dev/sda2 on / type jfs (rw,discard)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type jfs (rw,discard)
/dev/sdb1 on /home type jfs (rw)
gvfsd-fuse on /home/slackuser/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=slackuser)
slackuser@slackmachine:~$
I notice you only have 51G of storage left in /home? I could be mistaken but doesn't virtual box by default install the virtual disk image for guest os in /home/"user"/VirtualBox\ VMs/ ? If program runs but you dynamically allocated more than 51G to a guest os's virtual disk image I think you'd have issues?
I've installed virtualbox in a slackware vm with jfs as filesystem and all went ok. So, this is not the filesystem. Maybe the hdd has some trouble. smartctl -a /dev/sda could give some clue.
Didn't work. Also my /home is on a 2TB hd (but obviously filled with useless crap ) , I hope to remedy that when I get an external 8TB, but again, that should not affect this either. I am still open to other suggestions, before I format and reinstall 14.2 - and yes I did a full install also.
but the actual virtualizer itself, fails to build. I get an error saying
Quote:
Checking for Open Watcom:
** Open Watcom was not found!
Checking for iasl:
** iasl (variable IASL) not found!
Check /tmp/SBo/VirtualBox-5.0.14/configure.log for details
***** Checking Open Watcom *****
** Open Watcom was not found!
***** Checking iasl *****
** iasl (variable IASL) not found!
Seems the Watcom compiler is needed to build the virtualizer. There is no "Open Watcom" SlackBuild, and it appears that the community looks upon this package with disfavour. I've downloaded the open-watcom-c-linux-1.9 binary installer from ftp://ftp.openwatcom.org/pub. Should I just go ahead and run it?
And what is this IASL business?
Don't remember these difficulties when I installed on 14.1.....
then "All distributions (built on EL5 and therefore do not require recent system libraries) i386 | AMD64"
right click i386 link OR AMD64 link, save as
then back to first link look for
VirtualBox 5.0.24 Oracle VM VirtualBox Extension Pack All supported platforms
right click "All supported platforms", save as
in konsole in folder where saved to, as root:sh VirtualBox-5.0.24-108355-Linux_amd64.bin
when that's done, from where extensions link was saved, as root:
vboxmanage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.0.24-108355.vbox-extpack
but the actual virtualizer itself, fails to build. I get an error saying
The logfile contains:
Seems the Watcom compiler is needed to build the virtualizer. There is no "Open Watcom" SlackBuild, and it appears that the community looks upon this package with disfavour. I've downloaded the open-watcom-c-linux-1.9 binary installer from ftp://ftp.openwatcom.org/pub. Should I just go ahead and run it?
And what is this IASL business?
Don't remember these difficulties when I installed on 14.1.....
You're probably missing acpica, which is a required dependency of virtualbox. That is what adds support for iasl. There are no hard requirements for watcom and virtualbox runs fine without it (at least in my experience).
I was able to build virtualbox on a fresh 64bit 14.2 install without any problems. I just used sqg to generate a queue file (which just contains virtualbox-kernel, acpica, and finally virtualbox) and then had sbopkg build all the files.
It is running a VM of 64bit 14.2 right now that is working to build all my packages needed to eventually move my main system over to 14.2.
Slackware 14.2 is shipped with 4.4.14 kernel.
Seems you still runing 3.10.17 kernel from 14.1, please test the output of 'uname -r'.
Are you upgrade/install new kernel-* packages version 4.4.14:
Code:
$ ( cd /var/adm/packages ; ls kernel-* )
If yes,
- for MBR: are you rerun 'lilo' (may be after some edits on /etc/lilo.conf) to update the boot code?
- for UEFI: are you copy kernel to EFI partition?
If yes,
- for MBR: are you rerun 'lilo' (may be after some edits on /etc/lilo.conf) to update the boot code?
- for UEFI: are you copy kernel to EFI partition?
After the upgrade to 14.2, I followed the instructions listed here, to (re)installed GRUB2. I thought that was sufficient?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.