Author |
Message |
ruebe99
|
|
Post subject: virtualbox not operational after d-u
Posted: 02.01.2014, 08:43
|
|

Joined: 2010-09-11
Posts: 44
Status: Offline
|
|
With 3.12-6.slh.2-aptosid-amd64 x86_64 I get the message "[FAIL] Starting VirtualBox kernel modules[....] No suitable module for running kernel found ... failed!
failed!"
virtualbox is no longer operational with that latest kernel.
Cheers |
|
|
|
|
 |
DonKult
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 10:21
|
|
Team Member

Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
Sounds more like you have to rebuild the virtualbox module. If I remember right virtualbox moved to non-free recently(ish).
Or is boot really stopping at that message and does nothing else anymore?
(if so, its probably still not virtualbox, but something else. Booting without quiet might tell us more then) |
_________________ MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
|
|
|
 |
ruebe99
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 13:21
|
|

Joined: 2010-09-11
Posts: 44
Status: Offline
|
|
booted now without quiet. the virtualbox message when starting a box is "Kernel driver not installed (rc=-1908)" |
|
|
|
|
 |
towo
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 14:35
|
|

Joined: 2010-09-13
Posts: 522
Location: Pößneck / Thüringen
Status: Offline
|
|
What's hard to understand in "build the vbox-modules against the new kernel"? |
_________________
Code:
System: Host: Defiant Kernel: 4.15.0-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: Cinnamon 3.4.6
Distro: siduction 13.2.0 December - xfce - (201312310323)
|
|
|
|
 |
ruebe99
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 14:58
|
|

Joined: 2010-09-11
Posts: 44
Status: Offline
|
|
sorry - in the past dkms was processing all necessary things; but maybe I am wrong here |
|
|
|
|
 |
towo
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 15:00
|
|

Joined: 2010-09-13
Posts: 522
Location: Pößneck / Thüringen
Status: Offline
|
|
dkms status will tell you more.
And if dkms has not built the module, look in the buildlog to find out, what's wrong. |
_________________
Code:
System: Host: Defiant Kernel: 4.15.0-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: Cinnamon 3.4.6
Distro: siduction 13.2.0 December - xfce - (201312310323)
|
|
|
|
 |
ruebe99
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 15:27
|
|

Joined: 2010-09-11
Posts: 44
Status: Offline
|
|
dkms status is
virtualbox, 4.3.2: added
obviously the /var/lib/dkms/virtualbox/4.3.2/build is empty; where to find other logs? |
|
|
|
|
 |
towo
|
|
Post subject: RE: virtualbox not operational after d-u
Posted: 02.01.2014, 16:48
|
|

Joined: 2010-09-13
Posts: 522
Location: Pößneck / Thüringen
Status: Offline
|
|
virtualbox, 4.3.2: added
is not installed.
dkms build -m virtualbox -v 4.3.2 -k 3.12-6.slh.2-aptosid-amd64
if there is no error, then
dkms install -m virtualbox -v 4.3.2 -k 3.12-6.slh.2-aptosid-amd64 |
_________________
Code:
System: Host: Defiant Kernel: 4.15.0-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: Cinnamon 3.4.6
Distro: siduction 13.2.0 December - xfce - (201312310323)
|
|
|
|
 |
|