Your message dated Mon, 8 Feb 2016 20:18:57 +0000 (UTC)
with message-id <[email protected]>
and subject line Re: Bug#813617: virtualbox 5.0.14 for kernel 4.3.0-1-686-pae 
needs vboxdrv
has caused the Debian Bug report #813617,
regarding virtualbox 5.0.14 for kernel 4.3.0-1-686-pae needs vboxdrv
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
813617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813617
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: virtualbox
Version: 5.0.14-dfsg-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Using kernel 4.3.0-1-686-pae

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

starting virtualbox

   * What was the outcome of this action?

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 install virtualbox-dkms package 
and load the kernel module by executing
'modprobe vboxdrv'
as root. If it is available in your distribution, you should install the DKMS 
package first. This package keeps track of Linux kernel changes and recompiles 
the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support 
driver is not installed. On linux, open returned ENOEN

   * What outcome did you expect instead?

Nothing like that .-)

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), 
(500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox depends on:
ii  adduser                               3.113+nmu3
ii  init-system-helpers                   1.24
ii  libc6                                 2.21-7
ii  libcurl3-gnutls                       7.47.0-1
ii  libgcc1                               1:5.3.1-7
ii  libgsoap7                             2.8.22-2
ii  libpng12-0                            1.2.54-1
ii  libpython2.7                          2.7.11-3
ii  libsdl1.2debian                       1.2.15-12
ii  libssl1.0.2                           1.0.2f-2
ii  libstdc++6                            5.3.1-7
ii  libvncserver1                         0.9.10+dfsg-3+b1
ii  libvpx3                               1.5.0-2
ii  libx11-6                              2:1.6.3-1
ii  libxcursor1                           1:1.1.14-1+b1
ii  libxext6                              2:1.3.3-1
ii  libxml2                               2.9.3+dfsg1-1
ii  libxmu6                               2:1.1.2-2
ii  libxt6                                1:1.1.5-1
ii  procps                                2:3.3.11-3
ii  python                                2.7.11-1
ii  python2.7                             2.7.11-3
pn  python:any                            <none>
ii  virtualbox-dkms [virtualbox-modules]  5.0.14-dfsg-1
ii  zlib1g                                1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  11.1.1-2
ii  libqt4-opengl             4:4.8.7+dfsg-5
ii  libqtcore4                4:4.8.7+dfsg-5
ii  libqtgui4                 4:4.8.7+dfsg-5
ii  virtualbox-qt             5.0.14-dfsg-1

Versions of packages virtualbox suggests:
ii  vde2                            2.3.2+r586-2+b1
pn  virtualbox-guest-additions-iso  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
At the end it wasn't really a bug, just a missing kernel header

closing,

G.


Il Sabato 6 Febbraio 2016 10:04, "[email protected]" <[email protected]> ha scritto:
On Thu, Feb 04, 2016 at 03:49:38PM +0000, Gianfranco Costamagna wrote:
> >Nothig in the directorym, nothing in the file 
> when I ask you about a log I mean something like this:
> sudo apt-get install --reinstall virtualbox-dkms
> and everything printed in the terminal.

No problem, here we are:

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
  linux-image-3.16.0-4-686-pae linux-image-4.0.0-2-686-pae 
linux-image-4.1.0-1-686-pae linux-image-4.1.0-2-686-pae
  linux-image-4.2.0-1-686-pae
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.

OH!
done and grub updated....

0 aktualisiert, 0 neu installiert, 1 erneut installiert, 0 zu entfernen und 17 
nicht aktualisiert.
Es müssen noch 0 B von 637 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
(Lese Datenbank ... 477927 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../virtualbox-dkms_5.0.14-dfsg-2_all.deb ...

------------------------------
Deleting module version: 5.0.14
completely from the DKMS tree.
------------------------------
Done.
Entpacken von virtualbox-dkms (5.0.14-dfsg-2) über (5.0.14-dfsg-2) ...
virtualbox-dkms (5.0.14-dfsg-2) wird eingerichtet ...
Loading new virtualbox-5.0.14 DKMS files...
Building only for 4.3.0-1-686-pae
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Job for virtualbox.service failed because the control process exited with error 
code. See "systemctl status virtualbox.service"
and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.

I think I have to do it again ...
I first try to check linux headers...
    old headers purged, new ones installed
    grub undated


> e.g.
> "Building only for 4.3.0-1-amd64
> Building initial module blah
> done
> depmod
> DKMS:install completed
> and so on.
> this is what we need.

Crazy.
When one is doing the right things, everything works fine.
So do you need to have a look at all the files?
I'll attach them, but you need not read them :-)

RU:-)

--- End Message ---

Reply via email to