LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-21-2017, 08:05 AM   #16
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154

Quote:
Originally Posted by Didier Spaier View Post
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?
 
1 members found this post helpful.
Old 01-21-2017, 08:48 AM   #17
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Leinster, IE
Distribution: Slackware, NetBSD
Posts: 2,176

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by business_kid View Post
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!
 
Old 01-21-2017, 09:18 AM   #18
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,147

Original Poster
Rep: Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308
Quote:
Originally Posted by gezley View Post
There's a lot I miss about that Ireland too, of course!
I can imagine: Like the Guinness(& Murphy's, Beamish, Bulmer's, Bushmill's, Jameson's, poteen, etc. etc.) the craic, and the rain :-).
 
Old 01-21-2017, 10:17 AM   #19
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,147

Original Poster
Rep: Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308
Quote:
Originally Posted by kikinovak View Post
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.
 
Old 01-22-2017, 05:37 PM   #20
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Are you running the generic kernel, and is it up to date?
 
Old 01-23-2017, 04:24 AM   #21
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,147

Original Poster
Rep: Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308
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.

EDIT: I marked this solved because I updated Slackware, and virtualbox, so the initial issue was changed. The newer threads is:
http://www.linuxquestions.org/questi...ox-4175597655/

Last edited by business_kid; 01-23-2017 at 04:38 AM. Reason: Addition
 
Old 01-23-2017, 05:04 AM   #22
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by business_kid View Post
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.

Last edited by kikinovak; 01-23-2017 at 05:06 AM.
 
Old 01-23-2017, 12:02 PM   #23
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,147

Original Poster
Rep: Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308
REALLY Solved

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.
 
Old 01-23-2017, 03:16 PM   #24
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by business_kid View Post
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.

Cheers,

Niki
 
Old 01-28-2017, 04:36 AM   #25
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,147

Original Poster
Rep: Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308Reputation: 2308
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Virtualbox update actinide Linux - Newbie 9 01-23-2013 11:20 AM
LXer: VirtualBox Update -- 4.1.18 LXer Syndicated Linux News 0 06-29-2012 01:00 PM
[SOLVED] Unable to use VirtualBox after update michalng Debian 4 04-12-2011 04:14 AM
VirtualBox , after Fedora 12 update tor.ment0r Linux - Virtualization and Cloud 2 02-03-2010 09:35 AM
Virtualbox broken after update. custangro Ubuntu 7 06-07-2008 11:41 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration