Kernel 3.7.1 couldn't build module for virtualbox

[ayla]

As long as the meta package "linux-headers-siduction-$arch" is installed -as is the default on siduction- the headers come in automatically on every kernel update.

[orinoco]

I could have sworn that the package was installed once. It is now installed. Thanks for the hint.

[ayla]

hm, I remember I've missed it too a few weeks ago.
But I've played around with my system that time a lot, so I couldn't tell why it was missing.

greets
ayla

[hefee]

I could build the virtualbox driver again with virtualbox from experimental 4.1.18-dfsg-2.1

[hinto]

I ran into this using Fuduntu and VMPlayer.
-Hinto

[nox]

Hi,
could someone please explain the exact command sequence to fix this bug?
I'm still using kernel 3.6.x because of it .

Thank you!
Simon

[ayla]

Hi nox,

what exactly is your problem?

Installing virtualbox from virtualbox side?

This is shown here: http://forum.siduction.org/index.php?msg=26439#26439

Or missing Kernel-headers?

Code: [Select]

apt-get install linux-headers-siduction-amd64or

Code: [Select]

apt-get install linux-headers-siduction-686depending on the arch of your system.

Something else? Then please show us the output of the command(s) you've tried.

greets
ayla

[nox]

Hi ayla,

installing virtualbox or any other software from without the siduction/debian repos seems a little insecure to me and I'm afraid it could cause some system problems in future upgrades. I remember it not being a good practice...  But if I'm wrong please provide the exact link for my 686 system. I guess it's a dpgk -i install? Do I really have to remove my previous VB install? Dunno, maybe I should wait longer, seem a litle risky for a relative noob like me. Need some positive feedback before I move any further... a step by step guide would be awesome.

Cheers!
Simon

[Smon]

I use virtualbox-dkms from experimental, works fine here with 3.8

[ayla]

Hi,

I use virtualbox-dkms from experimental, works fine here with 3.8

This is AFAIK another way for a working vbox in between.
For this one you would have to do (in Runlevel 3):

Code: [Select]

apt-get update
apt-get dist-upgrade
touch /etc/apt/sources.list.d/debexp.list
echo >> /etc/apt/sources.list.d/debexp.list "deb http://ftp.de.debian.org/debian/ experimental main contrib non-free"
apt-get update
apt-get install -t experimental virtualbox virtualbox-dkms virtualbox-qt
You may remove the experimental repo after by editing /etc/apt/sources.list.d/debexp.list and set a # sign in front of the there existing line:

#deb http://ftp.de.debian.org/debian/ experimental main contrib non-free

But:
I've no problem here using vbox 4.2 from the virtualbox side.
Purging the old vbox did not remove my in vbox installed XP system. On the contrary I was surprised by installing vbox 4.2 I could use it again immediatly without any needed additional action -only had to add my user to the vboxuser line in /etc/group.
If you care of your systems stability you may remove the vbox repo from your sources-list again after installing vbox 4.2.

Sorry, I'm running out of time.

I will provide the commands for installing from virtualbox side in another post later.

greets
ayla

[Smon]

Sorry, I'm running out of time.

I will provide the commands for installing from virtualbox side in another post later.

Not necessary
You did it already here:
http://forum.siduction.org/index.php?topic=3097&postdays=0&postorder=asc#26439

To remove the vbox Repo only remove the added line

deb http://download.virtualbox.org/virtualbox/debian wheezy contrib

[ayla]

Not necessary
You did it already here:
http://forum.siduction.org/index.php?topic=3097&postdays=0&postorder=asc#26439

You're right, I edited this post lightly insteed, corrected a fault and added dkms to install.  Don't know what else to add.

greets
ayla

[Lanzi]

Seems to work fine her from experimental

root@Siduction:# apt-get install -t experimental  virtualbox  virtualbox-dkms

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.      
Statusinformationen werden eingelesen.... Fertig

Die folgenden zusätzlichen Pakete werden installiert:
  virtualbox-qt
Vorgeschlagene Pakete:
  vde2
Die folgenden Pakete werden aktualisiert (Upgrade):
  virtualbox virtualbox-dkms virtualbox-qt
3 aktualisiert, 0 neu installiert, 0 zu entfernen und 416 nicht aktualisiert.

Es müssen 17,5 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 25,6 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren [J/n]? j

Holen: 1 http://ftp.de.debian.org/debian/ experimental/main virtualbox-qt amd64 4.1.18-dfsg-2.1 [4.217 kB]
Holen: 2 http://ftp.de.debian.org/debian/ experimental/main virtualbox amd64 4.1.18-dfsg-2.1 [12,8 MB]
Holen: 3 http://ftp.de.debian.org/debian/ experimental/main virtualbox-dkms all 4.1.18-dfsg-2.1 [496 kB]                                                    
Es wurden 17,5 MB in 21 s geholt (797 kB/s).                                                                                                                
Lese Changelogs... Fertig
(Lese Datenbank ... 192328 Dateien und Verzeichnisse sind derzeit installiert.)


Vorbereitung zum Ersetzen von virtualbox-qt 4.1.18-dfsg-2 (durch .../virtualbox-qt_4.1.18-dfsg-2.1_amd64.deb) ...
Ersatz für virtualbox-qt wird entpackt ...
Vorbereitung zum Ersetzen von virtualbox 4.1.18-dfsg-2 (durch .../virtualbox_4.1.18-dfsg-2.1_amd64.deb) ...
Ersatz für virtualbox wird entpackt ...
Vorbereitung zum Ersetzen von virtualbox-dkms 4.1.18-dfsg-2 (durch .../virtualbox-dkms_4.1.18-dfsg-2.1_all.deb) ...

------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Ersatz für virtualbox-dkms wird entpackt ...
Trigger für hicolor-icon-theme werden verarbeitet ...
Trigger für menu werden verarbeitet ...
Trigger für shared-mime-info werden verarbeitet ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Trigger für man-db werden verarbeitet ...
Trigger für desktop-file-utils werden verarbeitet ...
virtualbox (4.1.18-dfsg-2.1) wird eingerichtet ...
[ ok ] Stopping VirtualBox kernel modules.
[FAIL] Starting VirtualBox kernel modules[....] No suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.
virtualbox-qt (4.1.18-dfsg-2.1) wird eingerichtet ...
virtualbox-dkms (4.1.18-dfsg-2.1) wird eingerichtet ...
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.8-0.towo.1-siduction-amd64
Building initial module for 3.8-0.towo.1-siduction-amd64
Done.

vboxdrv:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.8-0.towo.1-siduction-amd64/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.8-0.towo.1-siduction-amd64/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.8-0.towo.1-siduction-amd64/updates/dkms/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.8-0.towo.1-siduction-amd64/updates/dkms/

depmod....

DKMS: install completed.
[ ok ] Stopping VirtualBox kernel modules.
[ ok ] Starting VirtualBox kernel modules.
Trigger für menu werden verarbeitet ...