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.
About the road to get there, let me tell you that several decades ago it was only the Nationale 9 from Paris.
On the latest count, there are no less than four roads leading to Saint-Bauzille-de-Putois. One from Ferrières-les-Verreries, one from Notre-Dame-des-Landes, one from Laroque and one from Montoulieu. Paris? Now where's that?
Was that truck rigid? What a nightmare. Tractors in Ireland then had a narrower wheelbase, and fatalities from overturned tractors were common - the tractor would roll, throw the driver off, and then roll over him, usually killing him. It would be 25 kph max, and nobody would dare go much above walking speed on a bendy road.
Yes - a rigid truck. Even a fast-moving tractor was a pain when you had a full load because it took time to go back up through all the gears again (16 of them!) after you finally managed to overtake him. Meanwhile you just knew the tail of cars behind you were going mad at you for holding them up a second time. There's a lot I miss about that Ireland too, of course!
A little heads-up for Slackware users who want to install VirtualBox easily. I'm providing Slackware packages for Virtualbox 5.0.30 in my MLED [extras] repositories:
Make sure to download and install these three packages for your version and architecture:
virtualbox
virtualbox-kernel
virtualbox-extension-pack
VirtualBox depends on the acpica package, which is available in the main [desktop] repositories, in package group [d].
Add the following group to your system:
Code:
# groupadd -g 215 vboxusers
Add your user to this group:
Code:
# usermod -a -G vboxusers <youruser>
Last but not least, add the following stanza to /etc/rc.d/rc.local:
Code:
# Start vboxdrv
if [ -x /etc/rc.d/rc.vboxdrv ]; then
/etc/rc.d/rc.vboxdrv start
fi
Cheers,
Niki
In your honour, Niki, I downloaded the microlinux packages, removed everything virtualbox related I could find (VMs & all), installed as directed above, followed post-install mods as directed, and ended up that on a reboot, vboxdrv failed to install & sent me to dmesg. Dmesg reported
Code:
bash-4.3$ cat vbox-5.0.30.errs
[ 22.561392] vboxdrv: Unknown symbol __fentry__ (err 0)
[ 22.561416] vboxdrv: Unknown symbol contig_page_data (err 0)
[ 22.561425] vboxdrv: Unknown symbol preempt_notifier_inc (err 0)
[ 22.561435] vboxdrv: Unknown symbol preempt_notifier_register (err 0)
[ 22.561440] vboxdrv: Unknown symbol from_kgid (err 0)
[ 22.561449] vboxdrv: Unknown symbol from_kuid (err 0)
[ 22.561467] vboxdrv: Unknown symbol preempt_notifier_dec (err 0)
[ 22.561473] vboxdrv: Unknown symbol preempt_notifier_unregister (err 0)
Those errors have a familiar look to them. I can't install a VM for lack of the modules being loaded.
No, I'm running my own 4.4.38, but I also have the 4.4.14-huge kernel in lilo and have tried that with similar results. I never bother with the generic kernel because you have to organise an initrd and it's one more thing to go wrong. This way, I have 13M of modules and 5.1M of kernel in 4.4.38, vs 7.3M of kernel & 150M of modules for the 4.4.14-huge option.
No, I'm running my own 4.4.38, but I also have the 4.4.14-huge kernel in lilo and have tried that with similar results. I never bother with the generic kernel because you have to organise an initrd and it's one more thing to go wrong.
You do know that running the generic kernel with an initrd is the officially recommended way to go? Of course you can choose to do things your way, but then you get to keep the pieces.
Anyway, if you want my virtualbox-kernel package to work with your setup, using an updated generic kernel is mandatory.
I'm afraid I removed your packages again, along with everything virtualbox I could find including the VMs and started over with 5.1.12. I got that going, although I had to remake the running kernel in the source after a 'make distclean' and copy over the System.map, as the new one had some symbols the original didn't and virtualbox modules puked for the lack of them. I forgot to remove acpica, but you said it was a dependency. I don't see how. I don't have QT5 either.
I am thoroughly sick to the teeth of this, and will struggle with guest additions when I recover sufficiently.
There may have been stray stuff from old versions lying around but I don't really understand the refusal to work, or the thing working now.
I'm afraid I removed your packages again, along with everything virtualbox I could find including the VMs and started over with 5.1.12. I got that going, although I had to remake the running kernel in the source after a 'make distclean' and copy over the System.map, as the new one had some symbols the original didn't and virtualbox modules puked for the lack of them. I forgot to remove acpica, but you said it was a dependency. I don't see how. I don't have QT5 either.
I am thoroughly sick to the teeth of this, and will struggle with guest additions when I recover sufficiently.
There may have been stray stuff from old versions lying around but I don't really understand the refusal to work, or the thing working now.
VirtualBox 5.1.12 downloaded from virtualbox.org is an all-in-one package where everything is built-in, so you're ready-to-go. My packages on the other hand are dynamically linked, so they need stuff from the Slackware installation.
This being said, the important thing here is you got VirtualBox running on your installation.
A few things I have found out since, battling this (still). Currently, I get a web service error, warnings about my VMs, but everything works.
* Any Missing Symbols are missing from the running kernel & System.map. You have a kernel lacking some config option which VirtualBox needs.
* You cannot have built another kernel in your kernel source than the one you are running on, or you're very likely to get version magic errors. Cure is a 'make distclean' in the kernel source. That wipes the .config, so be sure to have it backed up. Then remake your running kernel config to get a correct Module.symvers.
* In /wherever_It's_Installed/VirtualBox/src/vboxhost/ there is the source of the kernel modules, along with a Makefile and a script, build_in_tmp. If you comment out the two lines at the end that say
Code:
rm -rf $tmpdir
it doesn't automatically wipe the tmpdirs & compiled modules. You can then run the script yourself with no options to see how modules build. I had best success going into each module's subdir and typing 'make,' and not using the top Makefile. There is a tangled maze of scripts calling scripts and inheriting options, & sourcing config files in this area. The whole package seems to disappear up it's own backside in this area and is very confusing.
* Lastly, if you're left wondering what kernel config option gives your particular missing symbol, a good way to find out is to search the kernel source with grep -r for your missing symbol. You want the file that EXPORTS it, which should be a .c file. Then, grep that .c file for the term CONFIG. That will list the kernel config options it references. You can usually run it down that way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.