Could not load 'vboxdrv' after upgrade to Ubuntu 16.04 (and I want to keep secure boot)

1

I had the same problem. After searching for a solution for days, I finally found an easy fix here: "gorka(dot)eguileor(dot)com(slash)vbox-vmware-in-secureboot-linux" (sorry can't fully post the link as I'm a new member)

If you have a Linux system running in Secure Boot and you install VirtualBox or VMware player you will see, with some frustration, that you won’t be able to run any VMs. I haven’t found any post that explains this properly, and most people suggest disabling Secure Boot as a solution and I find that to be a very poor solution, so here’s my 2 cents. Earlier picture shows what you’ll see from the GUI, but if you run it from the console you’ll see:

user@localhost:$

virtualbox

WARNING: The vboxdrv kernel module is not loaded. Either there is no module

available for the current kernel (3.15.8-200.fc20.x86_64) or it failed to

load. Please recompile the kernel module and install it by

sudo /etc/init.d/vboxdrv setup

You will...

0 0
2

At last, I solved this problem by reordering the booting order with the help from the mokutil author lcp, following this post fix this issue:https://github.com/lcp/mokutil/issues/11#issuecomment-356159399

1. Check whether MOK files exist.

$ sudo -i# cd /sys/firmware/efi/efivars# ls Mok*MokAuth-605dab50-e046-4300-abb6-3dd810dd8b23MokNew-605dab50-e046-4300-abb6-3dd810dd8b23MokSB-605dab50-e046-4300-abb6-3dd810dd8b23

2. Check the order of the boot.

# efibootmgr -vBootCurrent: 0000Timeout: 2 secondsBootOrder: 0000,0001,0002Boot0000* ubuntu HD(1,GPT,dabc2835-8f96-4429-ba98-3abadcfcaa57,0x800,0x82000)/File(\EFI\UBUNTU\GRUBX64.EFI)Boot0001* Windows Boot Manager HD(1,GPT,dabc2835-8f96-4429-ba98-3abadcfcaa57,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...d................Boot0002* ubuntu...
0 0
3

On Thu, May 6, 2010 at 4:37 PM, stan

[hidden email]

> wrote:

> I have built a 10.4 machine, and installed the Sun version of Viru

> tualBox on it. I installed this as oposed to the OSE version as I could not

> get the OSE version to work corectly, and the Sun version has some nice

> things not yet in the OSE version.

>

> Now I have updated the machine using apt-get, which brought in a new

> kernel. Unfortunatley this has broken VirtualBox.

>

> When I try to run /etc/init.d/vboxdrv start by hand, I get:

>

> root@pbuild3:/etc/init.d# ./vboxdrv start

> * Starting VirtualBox kernel module

> * modprobe vboxdrv failed. Please use 'dmesg' to find out why

>

> Looking at dnesg, I only see:

>

> [ 79.031511] warning: `VirtualBox' uses 32-bit capabilities (legacy

> support in use)

> [ 80.020096] Clocksource tsc unstable (delta =...

0 0
4

Oracle finally announced the stable release of Virtualbox 5.0, which provides increased security with encryption and improved performance.

According to the press release, the 5.0 release supports the latest guest or host operating systems including: Mac OS X Yosemite, Windows 10, Oracle Linux, Oracle Solaris, other Linux operating systems, and legacy operating systems. Oracle Virtualbox 5.0 also features:

Paravirtualization Support for Windows and Linux Guests Improved CPU Utilization Guest os can directly recognize USB 3.0 devices and operate at full 3.0 speeds On all host platforms, Windows, Linux and Oracle Solaris guests now support “drag and drop” of content between the host and the guest. Disk Image Encryption, using the industry standard AES algorithm with up to 256 bit data encryption keys (DEK).

There are also numerous of other changes and bug fixes, including:

New User Interface settings page for customizing status-bar, menu-bar and guest-content...
0 0
5

Following an UOS approved spec, Ubuntu is checking module signing by default, on kernels 4.4.0-18.34, 4.4.0-21.37, 4.2.0-42.49, 3.19.0-65.73 and 3.13.0-92.139 onwards. You can read more details in this bug in Launchpad.

Because of those changes, DKMS modules will not work on systems with Secure Boot enabled unless correctly configured.

In order to make DKMS work, Secure Boot signing keys for the system must be imported in the system firmware, otherwise Secure Boot needs to be disabled. There are several methods to configure your system to properly load DKMS modules with Secure Boot enabled.

Method 1 - Install the DKMS package you need

Simply install the package you need. Packages that make use of DKMS should prompt you to add new keys or disable Secure Boot, as appropriate for your system, and should do so automatically.

Method 2 - Disable Secure Boot from BIOS

Enter BIOS setup Disable secure boot Save configuration Reboot the system...
0 0
6

Apparently, many users of Ubuntu are reporting problem with laptop not going to suspend/sleep mode when the lid is closed. This is a confirmed bug in Ubuntu 16.04 and developers are working on a permanent fix to this problem. Seems like the problem may be due to hardware-kernel compatibility in some cases and for some, it is due to missing proprietary drivers. For now, the reasons are still vague and root cause is not yet determined as per the Ubuntu bug thread.

But don’t worry, there is a workaround to get through this problem by modifying the logind.conf file. Let’s get started. Note that it is important to first check if you have enabled the suspend settings for the laptop lid close setting in the ‘Power’ options.

Enable Laptop Lid Close Suspend/Sleep Action

Go to ‘Power’ settings and select ‘Suspend’ for the item “When the lid is closed”. You can do it for only the Battery power mode or also for ‘when plugged’ in option.

Once you have confirmed the...

0 0
7

VirtualBox recently reached a new major milestone.. version 5.2. This release brings lots of enhancements and changes, including unattended guest installation, VM export to Oracle Cloud, added experimental audio support for video recording and many more.

This brief tutorial shows students and new users how to install VirtualBox 5.2 on Ubuntu 17.04 / 17.10 Desktop / Server. If you’re reading this post then you probably know a thing or two about VirtualBox.

If you don’t, it’s a cross-platform virtualization software that allows you to run guest operating system inside a windows of the host computer. The guest machine can Windows, Linux or Mac operating systems.

VirtualBox is a powerful application that I’d recommend every IT student to download and install to create virtual labs. These labs can be a self-contained environments where you can test different applications and settings.

To install VirtualBox on Ubuntu servers, follow the steps below

...
0 0
8

Now that the Ubuntu 17.10 release is officially out many of you will be faced with the decision of whether to upgrade, or not.

In this post we’ll show how to upgrade to Ubuntu 17.10 from Ubuntu 17.04, plus provide a few pointers to those of you who want to upgrade from 16.04 LTS.

As we mention in our full Ubuntu 17.10 run-down, the latest short-term release is packed full of big changes and major additions. There’s a new desktop, a new display server, a new display manager, a new kernel, a new …Well, I’m sure you get the idea!

In all it’s a pretty compelling upgrade, especially if you’re currently running Ubuntu 17.04.

Prerequisites

Before attempting any Ubuntu upgrade there a couple of things you should always do.

First, make a backup of any/all important files and folders. While these shouldn’t get lost during the transition, there’s always an outside risk they might.

Secondly, make sure you have installed all updates to...

0 0
9

Problem Statement:

#1

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

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.

#2

Failed to open a session for the virtual machine “Windows XP”.

The virtual machine ‘Windows XP’ has terminated unexpectedly during startup with exit code 1.

(Running a virtual machine on VirtualBox the two dialogues would say that)

The cause — as the VirtualBox page states it:

Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes...

0 0
10

Today, I upgraded my Ubuntu 14.04 LTS system to Linux Kernel 4.4.4. Upgrade process went without any errors so far. However, Oracle VirtualBox didn’t work after upgrading to Kernel 4.4.4.

Whenever I started a new virtual machine, it showed the following error and didn’t let the guest machine to start.

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 '/sbin/rcvboxdrv setup' 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: sublibOsInit what:3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed, On linux, open returned ENOENT.

As you can see in the above screenshot, the error wizard says that you can fix the problem by running the...

0 0
11

Since Ubuntu kernel 4.4.0-20 the EFI_SECURE_BOOT_SIG_ENFORCE kernel config has been enabled. That prevents from loading unsigned third party modules if UEFI Secure Boot is enabled.

The easiest way to fix this issue is to disable Secure Boot in UEFI (BIOS) settings.

In most cases you can get into UEFI settings using grub menu. Press ESC button on booting, get into grub menu and select System Setup. Secure Boot option should be in "Security" or "Boot" section of the UEFI.

You can get into UEFI directly, but it depends on your hardware. Read your computer manual to see how to get there. It may be Del, or F2 on boot, or something else.

An alternative way is to disable Secure Boot using mokutil.

Since Ubuntu kernel build 4.4.0-21.37 this can be fixed by running

sudo apt install mokutil sudo mokutil --disable-validation

It will require to create a password. The password should be at least 8 characters long. After you reboot, UEFI will ask if you...

0 0