However, having an Arch Linux installation to tinker with and understand the Linux environment a little better is always useful. Most new users would probably prefer an out of the box solution like Debian or Fedora.
You might encounter an error at this point complaining about linux-headers, simply download the header package by apt-get install linux-headers-5.4.Arch Linux may not be for everyone. May need to re-install to current kernal. Using whatever plain text editors like gedit/scite/bashĪdd the following line to your /etc/apt/sources.list:Īdd Key, and combine with Downloading and Registering Open Terminal - Verify version / codename Now your operating system will start and you can now use VirtualBox without problem :) That you have previously entered, you will enter it and you will be informed that the operation has been completed successfully.
When you are inside the blue screen, select Enroll MOK > Continue > Yes > and it will ask you for the password A blue screen will appear with a keyboard wait, press the key that asks you to interrupt the boot. IMPORTANT! That will ask you for a password, put the one you want, you will only have to use it once in the next reboot. Then add it to the kernel: sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256.
generate the signature file: openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=VirtualBox/"ģ. Install the mkutil package to be able to do signed. That's why I get this error opening any machine in the Virtual Boxĭo the following steps to sign a driver, and it is loaded as a kernel module:ġ. This will happen if your computer has the SecureBoot mode activated, something very common in modern equipment. I think the problem is that the vboxdrv module is not signed and therefore not loaded with the kernel. This answer was tested only in Ubuntu and Debian 9 in my case, but maybe can works for you.
0 kommentar(er)
