Le 28/12/2014 06:27, Marc Shapiro a écrit :
Ooops! Sorry, Carl. This was supposed to go to the list.
On 12/27/2014 08:42 PM, Carl Fink wrote:
On Sat, Dec 27, 2014 at 08:29:38PM -0800, Marc Shapiro wrote:
... I have the following installed:
i linux-headers-3.16.0-0.bpo.4-amd64 - Header
files for
Linux 3.16.0-0.bpo.4-amd64
i A linux-headers-3.16.0-0.bpo.4-common - Common header
files
for Linux 3.16.0-0.bpo.4
i linux-image-3.16-0.bpo.2-amd64 - Linux
3.16 for
64-bit PCs
i linux-kbuild-3.16 -
Kbuild infrastructure for Linux 3.16
i A dkms - Dynamic Kernel Module Support Framework
i virtualbox-dkms - x86
virtualization solution - kernel module sources for dkms
i virtualbox - x86 virtualization solution - base binaries
i virtualbox-qt - x86 virtualization solution - Qt based user interface
I still get the above error when I start virtualbox. If I click past
it and
try to power up the ReactOS vm, I get:
----------------
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
there
is a permission problem with /dev/vboxdrv.
Please reinstall the kernel module by executing:
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install
the
DKMS package first. This package keeps track if Linux kernel changes
and
recompiles the vboxdrv kernel module if necessary.
-----------------
The problem is that '/etc/init.d/vboxdrv' does not exist. Neither does
'/dev/vboxdrv'. Am I somehow missing a package that should have been
installed? Have I missed a step somewhere in installing virtualbox?
How do
I get vboxdrv installed?
What version of virtualbox does the above represent?
In my experience dkms for VirtualBox has never worked in Wheezy. I
have to
manually compile the module every time I upgrade the kernel.
According to the Debian Wiki, you have to install VirtualBox from
backports
if you use a backports kernel:
https://wiki.debian.org/VirtualBox#Debian_7_.22Wheezy.22_Backports
Hmmm ... that's the x86 version of dkms for an AMD64 kernel. As this list
taught me some time ago, that can cause problems.
It was the Wheezy version of virtualbox, so I added contrib to the
wheezy-backports line in /etc/apt/sources.list. I then performed
'aptitude update' and 'aptitude -t wheezy-backports install virtualbox'
with the following results:
~# aptitude -t wheezy-backports install virtualbox
The following NEW packages will be installed:
libgsoap4{a}
The following packages will be REMOVED:
libgsoap2{u}
The following packages will be upgraded:
virtualbox virtualbox-dkms virtualbox-qt
3 packages upgraded, 1 newly installed, 1 to remove and 255 not upgraded.
Need to get 21.4 MB of archives. After unpacking 17.8 MB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox-qt amd64 4.3.14-dfsg-1~bpo70+1 [4,525 kB]
Get: 2 http://http.debian.net/debian/ wheezy-backports/main libgsoap4
amd64 2.8.16-2~bpo70+1 [545 kB]
Get: 3 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox amd64 4.3.14-dfsg-1~bpo70+1 [15.8 MB]
Get: 4 http://http.debian.net/debian/ wheezy-backports/contrib
virtualbox-dkms all 4.3.14-dfsg-1~bpo70+1 [575 kB]
Fetched 21.4 MB in 12s (1,712 kB/s)
Reading changelogs... Done
(Reading database ... 220323 files and directories currently installed.)
Preparing to replace virtualbox-qt 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox-qt_4.3.14-dfsg-1~bpo70+1_amd64.deb) ...
Unpacking replacement virtualbox-qt ...
Selecting previously unselected package libgsoap4:amd64.
Unpacking libgsoap4:amd64 (from
.../libgsoap4_2.8.16-2~bpo70+1_amd64.deb) ...
Preparing to replace virtualbox 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox_4.3.14-dfsg-1~bpo70+1_amd64.deb) ...
Unpacking replacement virtualbox ...
Processing triggers for menu ...
Processing triggers for man-db ...
Processing triggers for shared-mime-info ...
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'
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
(Reading database ... 220353 files and directories currently installed.)
Removing libgsoap2 ...
(Reading database ... 220338 files and directories currently installed.)
Preparing to replace virtualbox-dkms 4.1.18-dfsg-2+deb7u3 (using
.../virtualbox-dkms_4.3.14-dfsg-1~bpo70+1_all.deb) ...
------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement virtualbox-dkms ...
dpkg: warning: unable to delete old directory
'/usr/src/virtualbox-4.1.18/vboxdrv': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/src/virtualbox-4.1.18': Directory not empty
Setting up libgsoap4:amd64 (2.8.16-2~bpo70+1) ...
Setting up virtualbox (4.3.14-dfsg-1~bpo70+1) ...
[ 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.
Setting up virtualbox-qt (4.3.14-dfsg-1~bpo70+1) ...
Setting up virtualbox-dkms (4.3.14-dfsg-1~bpo70+1) ...
Loading new virtualbox-4.3.14 DKMS files...
Building only for 3.16-0.bpo.2-amd64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
[ 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.
Processing triggers for menu ...
I still get the same errors on starting virtualbox, or powering up any
vm. There is still no file '/etc/init.d/vboxdrv'.
How do I manually compile the module?
Hello,
When i want to install VBox on Debian, i prefer installing the
"module-assistant" package and using the cmd "m-a prepare". It'll
download all necessary packages to build module.
Next, you can install VBox, it sould be OK as in my system.
--
Nicolas D.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/549fd72b.7090...@gmail.com
