VirtualBox 4.2.14-Modules from Rigo 'NOT FOUND' [Solved]

Anything that pertains to Entropy, Equo or Sulfur

Moderator: Moderators

VirtualBox 4.2.14-Modules from Rigo 'NOT FOUND' [Solved]

Postby linuxfluesterer » Thu Jul 11, 2013 12:00

Hallo guys.
What you see here is my installed Kernel:
Code: Select all
 @@ Paket: sys-kernel/linux-sabayon-3.9.7 Branch: 5, [sabayonlinux.org]
>>         Verfügbar:      Version: 3.9.7 ~ tag: NoTag ~ Version: 0
>>         Installiert:    Version: 3.9.7 ~ tag: NoTag ~ Version: 0
>>         Slot:           3.9
>>         Homepage:       https://github.com/Sabayon/kernel
>>         Beschreibung:   Official Sabayon Linux Standard
>>                         kernel image
>>         Lizenz:         GPL-2 freedist

SL-K39-KDE410 ~ # uname --a
Linux SL-K39-KDE410 3.9.0-sabayon #1 SMP Thu Jun 27 07:53:45 UTC 2013 x86_64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz GenuineIntel GNU/Linux

I run Sabayon from Daily Build (26/06/2013), KDE with upgrades after.
Then I wanted to install VirtualBox 4.2.14 with Rigo.
So I've installed:
VirtualBox Bin 4.2.14
VirtualBox Modules 4.2.14#3.9.0-sabayon
VirtualBox Guest Additions 4.2.14#3-9-0-sabayon
'vboxusers' is added to my personal groups. I did a reboot.
But now, when I will start VirtualBox, I get the message, that I have to load the vbox-modules.
Ok, so I will load the modules
vboxdrv
vboxnetflt
vboxnetadp
as root with modprobe, but then I receive the error message:
Code: Select all
modprobe: FATAL: Module vboxdrv not found.

Here's my directory /lib64/modules/3.9.0-sabayon/misc:
Code: Select all
SL-K39-KDE410 ~ # ls -lan /lib64/modules/3.9.0-sabayon/misc
insgesamt 2388
drwxr-xr-x 2 0 0     119 11. Jul 12:05 .
drwxr-xr-x 7 0 0    4096 11. Jul 12:05 ..
-rw-r--r-- 1 0 0  385056 26. Jun 19:07 ndiswrapper.ko
-rw-r--r-- 1 0 0   55456 26. Jun 19:03 nvidiabl.ko
-rw-r--r-- 1 0 0 1916704  5. Jul 16:28 vboxdrv.ko
-rw-r--r-- 1 0 0   11912  5. Jul 16:28 vboxnetadp.ko
-rw-r--r-- 1 0 0   29608  5. Jul 16:28 vboxnetflt.ko
-rw-r--r-- 1 0 0   29464  5. Jul 16:28 vboxpci.ko

which proofs, that the modules, I've installed with Rigo are located in the right (Kernel) dierectory.
So, why are those modules are not loaded then?
Does anyone here experience the same problem?
I've checked, I use only one Kernel (Sabayon 3.9.7), I use systemd, I run KDE 4.10.4.

-Linuxfluesterer (I love KDE ...)
Last edited by linuxfluesterer on Tue Jul 16, 2013 6:24, edited 1 time in total.
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 702
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: VirtualBox 4.2.14-Modules from Rigo 'NOT FOUND'

Postby linuxfluesterer » Tue Jul 16, 2013 6:23

Hallo guys.
In between I have made a new Sabayon installation from 07/07/2013 with Kernel 3.10-r2 and (still) KDE 4.10.4.
And I have been searching in forum's archive until I have found this:
https://forum.sabayon.org/viewtopic.php?f=58&t=30011&p=162944&hilit=virtualbox#p162930

Finally this was the best solution to my problem installing the correct VirtualBox.bin
So I also installed the matching modules and guest additions the same way (in a root terminal).
Adding 'vboxusers' to my personal group and starting the modules:
Code: Select all
vboxdrv
vboxnetadp
vboxnetflt

manually, and then started
Code: Select all
VirtualBox
as user, this program, version 4.2.14, is started properly and I can add existing Virtual images.
The point is, that the modules (vbox...) are NOT loaded automatically when boot, though they are part of file /etc/conf.d/modules:
Code: Select all
...
modules="vboxdrv vboxnetflt vboxnetadp"

So, long time, I guessed, why not loaded. In Sabayon versions before, those modules were always started with boot.
Then I assumed the answer in systemd.
And right, in systemd protocol, additional modules to be loaded at boot time must be placed in
Code: Select all
/etc/modules-load.d/
insgesamt 16
drwxr-xr-x   2 0 0   59 15. Jul 09:36 .
drwxr-xr-x 152 0 0 8192 15. Jul 05:53 ..
-rw-r--r--   1 0 0    0 26. Jun 14:45 .keep_sys-apps_systemd-0
-rw-r--r--   1 0 0   96 15. Jul 09:36 Virtualbox.conf

and (in my case for VirtualBox) look like this:
Code: Select all
cat /etc/modules-load.d/Virtualbox.conf
# Module fuer virtualBox, mit Systemd geladen
# Stand: 15/07/2013
vboxdrv
vboxnetadp
vboxnetflt

Then, in case the systemd-modules-load.service is not started, you'll need to do then as root with:
Code: Select all
systemctl enable systemd-modules-load.service

Hint: I have found most systemd services for Sabayon in /usr/lib/systemd/system
Then after reboot, all modules in /etc/modules-load.d directory with ext .conf will be loaded at boot time.
For a closer look, watch this:
Code: Select all
http://www.freedesktop.org/software/systemd/man/modules-load.d.html


Hope to help anyone else here.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 702
Joined: Thu Sep 20, 2012 19:47
Location: Germany


Return to Entropy|Equo|Rigo Package Managers

Who is online

Users browsing this forum: No registered users and 3 guests