Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Geier0815 on 2012/12/18, 08:47:56
-
Hi all,
d-u this morning install kernel 3.7.1 witch is not able to build the virtualbox-module.
DKMS make.log for virtualbox-4.1.18 for kernel 3.7-1.towo-siduction-amd64 (x86_64)
Di 18. Dez 08:31:35 CET 2012
make: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
LD /var/lib/dkms/virtualbox/4.1.18/build/built-in.o
LD /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/built-in.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’:
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: error: ‘VM_RESERVED’ undeclared (first use in this function)
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Fehler 1
make[1]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv] Fehler 2
make: *** [_module_/var/lib/dkms/virtualbox/4.1.18/build] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
Moin Moin,
d-u installiert den Kernel 3.7.1 welcher nicht in der Lage ist das Module für virtualbox zu bauen. Also Augen auf!
-
und mit Version 4.2?
greetz
devil
-
They are working on it:
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1086030.html
If I knew how to use deb diffs..
But it looks like a fix will be available in days.
-
Version 4.2.4 from Oracle was running fine with Kernel 3.7-0 and
is running fine too after dist-upgrade and Kernel 3.7-1 with no need to act on it.
greets ayla
Edit:
Short description how I installed it:
apt-get purge virtualbox
added:
deb http://download.virtualbox.org/virtualbox/debian wheezy contrib to one of my sources.list in /etc/apt/sources.list.d/
apt-get update
apt-get install virtualbox-4.2 dkms
The new installation has found my old guest system. I hadn't done anything else, except adding my user to group vboxusers in /etc/group, just works.
ahm... If the extensionpack for 4.18 was installed, vbox will detect it and ask whether it should get updatet.
Good idea to say "yes". ;)
-
It works - although I had to purge the vboxadditions iso too:
apt-get purge virtualbox-guest-additions-iso
-
Does it work with dkms?
-
hmm, I guess so:
ls -l /var/lib/dkms/vboxhost/4.2.4/3.7-1.towo-siduction-amd64/x86_64/module/
insgesamt 2008
-rw-r--r-- 1 root root 1973560 Dez 18 09:03 vboxdrv.ko
-rw-r--r-- 1 root root 12296 Dez 18 09:03 vboxnetadp.ko
-rw-r--r-- 1 root root 30464 Dez 18 09:03 vboxnetflt.ko
-rw-r--r-- 1 root root 30640 Dez 18 09:03 vboxpci.ko
-
Hi,
similar problem here.
Vbox 4.2.4 was working fine with kernel 3.6-6 and dkms installed.
Did a d-u this morning pulling in kernel 3.7-1. Virtualbox complained about missing kernel modules./etc/init.d/vboxdrv setup didn't help.
I purged virtualbox and installed newest version 4.2.6. Same result~$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.7-1.towo-siduction-amd64) or it failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
Any help would be appreciated.
Gruß
oduffo
-
Problem solved due to some hints in the vbox-forums.
I reinstalled the linux-kernel-headers and did a reboot.
The latter I should have done in the first place.
Gruß
oduffo (who is happy again)
-
What is the most secure strategy to solve the prob?
DKMS make.log for virtualbox-4.1.18 for kernel 3.7-3.towo-siduction-amd64 (x86_64)
So 20. Jan 13:51:59 CET 2013
make: Entering directory `/usr/src/linux-headers-3.7-3.towo-siduction-amd64'
LD /var/lib/dkms/virtualbox/4.1.18/build/built-in.o
LD /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/built-in.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
CC [M] /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’:
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: error: ‘VM_RESERVED’ undeclared (first use in this function)
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Fehler 1
make[1]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv] Fehler 2
make: *** [_module_/var/lib/dkms/virtualbox/4.1.18/build] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.7-3.towo-siduction-amd64'
Do I just apt-get purge linux-kernel-headers and install them again?
-
@mylo,
first of all I would install latest version of virtualbox 4.2.6 from Oracle.
Gruß
oduffo
-
I installed VBox 4.2.6 for kernel 3.7-1 but don't recall if it built module with dkms. Dist-upgrade today brought in kernel 3.7-3 but module did not build with dkms. It built OK manually.
Should it build with dkms?
Headers are installed, virtualbox-dkms package is not available for VBox 4.2.6. I am in vboxusers group.
apt-cache policy virtualbox-dkms
virtualbox-dkms:
Installed: (none)
Candidate: 4.1.18-dfsg-2
Version table:
4.1.18-dfsg-2 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
-
Should it build with dkms?
It had build here (twice now, for 3.7-2 and 3.7-3).
Just
apt-get install dkms
virtualbox-dkms is not needed for the Oracle module.
Greets
ayla
-
apt-cache policy dkms
dkms:
Installed: 2.2.0.3-1.2
Installed already. Oh well, only a small problem as it built manually.
-
Why aren't the matching headerfiles automatically installed if d-u brings a new kernal? Without this all dkms tasks are failling (virtualbox-oracle, fglrx, etc.) as long I install the propper header-files by hand. My fault?
-
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.
-
I could have sworn that the package was installed once. It is now installed. Thanks for the hint.
-
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
-
I could build the virtualbox driver again with virtualbox from experimental 4.1.18-dfsg-2.1
-
I ran into this using Fuduntu and VMPlayer.
-Hinto
-
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
-
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?
apt-get install linux-headers-siduction-amd64or
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
-
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
-
I use virtualbox-dkms from experimental, works fine here with 3.8
-
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):
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
-
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
-
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
-
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 ...