severity 636572 important
tag 636572 confirmed
thanks
I request a change of the severity at least to important : the package is
not usable for me.
If more info is required, please ask what kind.
regards,
I have the same problem.
I installed virtualbox-ose, virtualbox-ose-dkms and linux-headers-amd64.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I have managed to build vboxdrv manually, thusly:
cd /usr/src/virtualbox-4.0.10/vboxdrv
make
make install
modprobe vboxdrv
and virtual machines are now willing to start. The syntax for dkms was
just too hairy, at first glance of the man page
Clayton
--
To UNSUBSCRIBE, email to debian-bug
On Thu, 04 Aug 2011 11:09:36 +0200
Felix Geyer wrote:
> On 04.08.2011 10:53, clayton wrote:
> > but dkms still does seem to have been triggered to build a vboxdrv
> > module:
>
> dkms had a bug causing it to not properly trigger module builds,
> see http://bugs.debian.org/634979
>
> Have you ha
On 04.08.2011 10:53, clayton wrote:
but dkms still does seem to have been triggered to build a vboxdrv module:
dkms had a bug causing it to not properly trigger module builds,
see http://bugs.debian.org/634979
Have you had dkms 2.2.0.1-1 - 2.2.0.1-3 installed while
installing/upgrading virtual
Package: virtualbox
Version: 4.0.10-dfsg-1
Severity: important
This is a machine that tracks Testing, which I installed in the last few days.
Whenever I try to
start a virtualbox machine, I get the error:
"Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv'
as root."
6 matches
Mail list logo
