Freya Virtualbox error after update

Discussion in 'Newbie Questions' started by brandy, Sep 13, 2016.

  1. brandy

    brandy Thread Starter
    Expand Collapse
    Member

    Joined:
    Sep 12, 2016
    Messages:
    5
    Likes Received:
    0
    Hi!

    I´m running Virtualbox on my fresh installed Elementary. After a update a few days ago I get an error "Kernel driver not installed". (I attached a screenshot)

    I tried different things, which I found on the Internet, for example

    - reinstall dkms
    - /etc/init.d/vboxdrv setup (didnt´t work)

    What should I do now?
    Thanks a lot!
     

    Attached Files:

  2. paradise

    paradise
    Expand Collapse
    Elementary Supporter

    Joined:
    Dec 3, 2014
    Messages:
    128
    Likes Received:
    34
    Heyho brandy,

    can you try to post the output from "sudo /etc/init.d/vboxdrv setup" ? The issue itself seems to happen because the kernel has been updated, which conflicts with the virtualbox-setup before (compiled depending on the old kernel).

    Have you already tried to reinstall the package virtualbox-dkms? (from https://ubuntuforums.org/showthread.php?t=1885936)

    Code (Text):
    sudo apt-get remove virtualbox-dkms
    sudo apt-get install virtualbox-dkms
     
  3. brandy

    brandy Thread Starter
    Expand Collapse
    Member

    Joined:
    Sep 12, 2016
    Messages:
    5
    Likes Received:
    0
  4. paradise

    paradise
    Expand Collapse
    Elementary Supporter

    Joined:
    Dec 3, 2014
    Messages:
    128
    Likes Received:
    34
    I am not sure how SecureBoot affects the Virtualbox, sorry. But another try could be the hint in the comments at http://elementaryos.stackexchange.com/questions/3872/vbox-kernel-driver-not-installed-rc-1908:

    @ThomasShera , you better try with sudo apt-get install linux-generic (This should cover when your installed kernel is absolute). other way sudo apt-get dist-upgrade ; sudo linux-headers-`uname -r` . it means you have to update your kernel. – user.dz

    You should give it a try, maybe it help when you download the linux-header-packages this way:

    Code (Text):
    sudo apt-get install linux-generic #or
    sudo apt-get dist-upgrade ; sudo apt-get install linux-headers-`uname -r`
     
    #4 paradise, Sep 14, 2016
    Last edited: Sep 14, 2016
  5. brandy

    brandy Thread Starter
    Expand Collapse
    Member

    Joined:
    Sep 12, 2016
    Messages:
    5
    Likes Received:
    0
    On executing

    Code (Text):
    sudo apt-get remove virtualbox-dkms
    I got the message, that dkms is not installed, although it was in the software center.
    On installing it, I got following message:

    Code (Text):

    DKMS: install completed.
    * Stopping VirtualBox kernel modules  [ OK ]
    * Starting VirtualBox kernel modules  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
      [fail]
    invoke-rc.d: initscript virtualbox, action "restart" failed.
    Trigger für shim-signed (1.18~14.04.1+0.8-0ubuntu2) werden verarbeitet ...
    Whats wrong here?
    dmesg gives a long list - do you want to see it?
     
  6. paradise

    paradise
    Expand Collapse
    Elementary Supporter

    Joined:
    Dec 3, 2014
    Messages:
    128
    Likes Received:
    34
    :-( seems connected with http://unix.stackexchange.com/questions/282265/starting-virtualbox-kernel-modules-failed

    i think the best would be, you disable secure boot in BIOS first, so we are sure that SecureBoot isn't the issue. afterwards, what is the output when you try to install the package dkms + the outpout from --get-selections (show installed packages):

    Code (Text):
    sudo apt-get install dkms
    #and check the installed dkms* packages:
    sudo dpkg --get-selections | grep dkms
     
  7. brandy

    brandy Thread Starter
    Expand Collapse
    Member

    Joined:
    Sep 12, 2016
    Messages:
    5
    Likes Received:
    0
    But why did it work before the update with Secure Boot?
    No matter, I will try it!

    Thank you!
     
  8. brandy

    brandy Thread Starter
    Expand Collapse
    Member

    Joined:
    Sep 12, 2016
    Messages:
    5
    Likes Received:
    0
    Secure Boot was the answer!
    I just changed it in BIOS and Virtualbox works perfectly now...

    Thanks a lot!
     

Share This Page

Loading...