How do I install the virtualbox-dkms package?“Failed to start LSB: VirtualBox Linux kernel module”reconfiguration issues with dpkgCan't make machines in VirtualBoxVirtualbox , Ubuntu 11.10 , linux-kernel 3: cannot start virtual machineUnable to install VirtualBox on Ubuntu 12.10: Kernel headers cannot be foundVirtualBox - Error not suplibOsinitCannot start virtualbox VM's: Kernel driver is not installedInstalling ndiswrapper-dkms on ubuntu 12.04AMD legacy driver installation failed due to missing kernel headersVirtualBox error kernel headersVirtualBox not installing on Ubuntu 14.04 LTScan't install Realtek RTL8723de on ubuntu 16.04 kernel 4.15Updated to 4.15.0-29.31 Ubuntu 18.04, and my wifi and ethernet stopped working
Has the laser at Magurele, Romania reached a tenth of the Sun's power?
What is going on with gets(stdin) on the site coderbyte?
Is there a RAID 0 Equivalent for RAM?
Is there a way to have vectors outlined in a Vector Plot?
How to convince somebody that he is fit for something else, but not this job?
Is this toilet slogan correct usage of the English language?
Strong empirical falsification of quantum mechanics based on vacuum energy density?
Is this part of the description of the Archfey warlock's Misty Escape feature redundant?
Make a Bowl of Alphabet Soup
"Oh no!" in Latin
How to preserve electronics (computers, iPads and phones) for hundreds of years
Stack Interview Code methods made from class Node and Smart Pointers
How do you make your own symbol when Detexify fails?
Pre-mixing cryogenic fuels and using only one fuel tank
Why does this expression simplify as such?
What is Cash Advance APR?
Which was the first story featuring espers?
What does "Scientists rise up against statistical significance" mean? (Comment in Nature)
A variation to the phrase "hanging over my shoulders"
What fields between the rationals and the reals allow a good notion of 2D distance?
Does the Linux kernel need a file system to run?
Do we have to expect a queue for the shuttle from Watford Junction to Harry Potter Studio?
It grows, but water kills it
Doesn't the system of the Supreme Court oppose justice?
How do I install the virtualbox-dkms package?
“Failed to start LSB: VirtualBox Linux kernel module”reconfiguration issues with dpkgCan't make machines in VirtualBoxVirtualbox , Ubuntu 11.10 , linux-kernel 3: cannot start virtual machineUnable to install VirtualBox on Ubuntu 12.10: Kernel headers cannot be foundVirtualBox - Error not suplibOsinitCannot start virtualbox VM's: Kernel driver is not installedInstalling ndiswrapper-dkms on ubuntu 12.04AMD legacy driver installation failed due to missing kernel headersVirtualBox error kernel headersVirtualBox not installing on Ubuntu 14.04 LTScan't install Realtek RTL8723de on ubuntu 16.04 kernel 4.15Updated to 4.15.0-29.31 Ubuntu 18.04, and my wifi and ethernet stopped working
I am getting the following error when attempting to install the VirtualBox kernel modules :
------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.5.0-17-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
I have tried installing the linux-source package, but I am not sure how Ubuntu handles kernel sources and headers.
Any ideas on how to do this from an Ubuntu standpoint?
kernel virtualbox
edited 24 mins ago
Kevin Bowen
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
add a comment |
I am getting the following error when attempting to install the VirtualBox kernel modules :
------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.5.0-17-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
I have tried installing the linux-source package, but I am not sure how Ubuntu handles kernel sources and headers.
Any ideas on how to do this from an Ubuntu standpoint?
kernel virtualbox
edited 24 mins ago
Kevin Bowen
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
add a comment |
I am getting the following error when attempting to install the VirtualBox kernel modules :
------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.5.0-17-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
I have tried installing the linux-source package, but I am not sure how Ubuntu handles kernel sources and headers.
Any ideas on how to do this from an Ubuntu standpoint?
kernel virtualbox
edited 24 mins ago
Kevin Bowen
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
I am getting the following error when attempting to install the VirtualBox kernel modules :
------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.5.0-17-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
I have tried installing the linux-source package, but I am not sure how Ubuntu handles kernel sources and headers.
Any ideas on how to do this from an Ubuntu standpoint?
kernel virtualbox
kernel virtualbox
edited 24 mins ago
Kevin Bowen
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
edited 24 mins ago
Kevin Bowen
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
edited 24 mins ago
Kevin Bowen
14.7k155970
edited 24 mins ago
Kevin Bowen
14.7k155970
edited 24 mins ago
Kevin Bowen
14.7k155970
14.7k155970
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
asked Oct 20 '12 at 14:24
Bill DenglerBill Dengler
106113
106113
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
My Virtual Box told me that the kernel drivers were not installed. I ran
sudo apt-get remove virtualbox-dkms
to remove the drivers and then re-installed them
sudo apt-get install virtualbox-dkms
which rebuilt the drivers and I was able to run virtualbox with no problems
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
1
Or using --reinstall option:sudo apt install --reinstall virtualbox-dkms
– visoft
Feb 25 '18 at 10:08
add a comment |
An other way:
apt-get install linux-headers-`uname -r`
dpkg-reconfigure virtualbox-dkms
The normal way:
/etc/init.d/vboxdrv setup
edited Apr 5 '17 at 21:41
Kenny Loveall
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
1
Wonder why “an other way” is mentioned before the “normal” one. However,dpkg-reconfigureseems to be the right option.
– Melebius
Oct 5 '16 at 12:17
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:sudo apt-get install linux-headers-`uname -r`thensudo dpkg-reconfigure virtualbox-dkmsand finallysudo dpkg-reconfigure virtualbox
– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
add a comment |
You need the kernel header as well. Based on your output, sudo apt-get install kernel-headers-3.5.0-17-generic should do it. On the guest VM, either autorun the ISO image or sudo sh ./VBoxLinuxAdditions.run from the shell prompt should work. Appears this is a known problem with the latest 12.10 release.
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
add a comment |
Didn't work for me. Solved it by running:
gksudo synaptic
Search for 'dkms' and (re)install the one for VirtualBox and press the 'Apply' button. The output should say that virtualbox kernel drivers are up and running.
edited Jul 17 '15 at 0:36
simplify
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
add a comment |
This is caused by the kernel headers not being available. These headers are not typically required, but help other applications need them to build kernel modules to keep in sync with your distribution and the version you are using.
You can install specific headers, or you can install 'generic', or 'current':
sudo apt install linux-headers-generic
This will ensure that when you take in new kernels, the headers of those kernels are also installed. When you update your kernel, VirtualBox will be able to update itself with the newest, matching headers. Sometimes these can be found by other names, such as linux-headers-amd64, in other distributions.
After you have the headers, you can purge/re-install VirtualBox, or have VirtualBox rebuild the modules and complete the setup:
sudo dpkg-reconfigure virtualbox-dkms
sudo modprobe vboxdrv
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f203586%2fhow-do-i-install-the-virtualbox-dkms-package%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
My Virtual Box told me that the kernel drivers were not installed. I ran
sudo apt-get remove virtualbox-dkms
to remove the drivers and then re-installed them
sudo apt-get install virtualbox-dkms
which rebuilt the drivers and I was able to run virtualbox with no problems
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
1
Or using --reinstall option:sudo apt install --reinstall virtualbox-dkms
– visoft
Feb 25 '18 at 10:08
add a comment |
My Virtual Box told me that the kernel drivers were not installed. I ran
sudo apt-get remove virtualbox-dkms
to remove the drivers and then re-installed them
sudo apt-get install virtualbox-dkms
which rebuilt the drivers and I was able to run virtualbox with no problems
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
1
Or using --reinstall option:sudo apt install --reinstall virtualbox-dkms
– visoft
Feb 25 '18 at 10:08
add a comment |
My Virtual Box told me that the kernel drivers were not installed. I ran
sudo apt-get remove virtualbox-dkms
to remove the drivers and then re-installed them
sudo apt-get install virtualbox-dkms
which rebuilt the drivers and I was able to run virtualbox with no problems
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
My Virtual Box told me that the kernel drivers were not installed. I ran
sudo apt-get remove virtualbox-dkms
to remove the drivers and then re-installed them
sudo apt-get install virtualbox-dkms
which rebuilt the drivers and I was able to run virtualbox with no problems
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
edited Nov 23 '18 at 10:32
abu_bua
3,98181430
3,98181430
answered Oct 21 '12 at 19:37
KevinKevin
1412
answered Oct 21 '12 at 19:37
KevinKevin
1412
answered Oct 21 '12 at 19:37
KevinKevin
1412
1412
1
Or using --reinstall option:sudo apt install --reinstall virtualbox-dkms
– visoft
Feb 25 '18 at 10:08
add a comment |
1
Or using --reinstall option:sudo apt install --reinstall virtualbox-dkms
– visoft
Feb 25 '18 at 10:08
1
1
Or using --reinstall option:
sudo apt install --reinstall virtualbox-dkms– visoft
Feb 25 '18 at 10:08
Or using --reinstall option:
sudo apt install --reinstall virtualbox-dkms– visoft
Feb 25 '18 at 10:08
add a comment |
An other way:
apt-get install linux-headers-`uname -r`
dpkg-reconfigure virtualbox-dkms
The normal way:
/etc/init.d/vboxdrv setup
edited Apr 5 '17 at 21:41
Kenny Loveall
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
1
Wonder why “an other way” is mentioned before the “normal” one. However,dpkg-reconfigureseems to be the right option.
– Melebius
Oct 5 '16 at 12:17
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:sudo apt-get install linux-headers-`uname -r`thensudo dpkg-reconfigure virtualbox-dkmsand finallysudo dpkg-reconfigure virtualbox
– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
add a comment |
An other way:
apt-get install linux-headers-`uname -r`
dpkg-reconfigure virtualbox-dkms
The normal way:
/etc/init.d/vboxdrv setup
edited Apr 5 '17 at 21:41
Kenny Loveall
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
1
Wonder why “an other way” is mentioned before the “normal” one. However,dpkg-reconfigureseems to be the right option.
– Melebius
Oct 5 '16 at 12:17
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:sudo apt-get install linux-headers-`uname -r`thensudo dpkg-reconfigure virtualbox-dkmsand finallysudo dpkg-reconfigure virtualbox
– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
add a comment |
An other way:
apt-get install linux-headers-`uname -r`
dpkg-reconfigure virtualbox-dkms
The normal way:
/etc/init.d/vboxdrv setup
edited Apr 5 '17 at 21:41
Kenny Loveall
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
An other way:
apt-get install linux-headers-`uname -r`
dpkg-reconfigure virtualbox-dkms
The normal way:
/etc/init.d/vboxdrv setup
edited Apr 5 '17 at 21:41
Kenny Loveall
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
edited Apr 5 '17 at 21:41
Kenny Loveall
134
edited Apr 5 '17 at 21:41
Kenny Loveall
134
edited Apr 5 '17 at 21:41
Kenny Loveall
134
134
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
answered May 4 '13 at 10:55
Marc QuintonMarc Quinton
12713
12713
1
Wonder why “an other way” is mentioned before the “normal” one. However,dpkg-reconfigureseems to be the right option.
– Melebius
Oct 5 '16 at 12:17
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:sudo apt-get install linux-headers-`uname -r`thensudo dpkg-reconfigure virtualbox-dkmsand finallysudo dpkg-reconfigure virtualbox
– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
add a comment |
1
Wonder why “an other way” is mentioned before the “normal” one. However,dpkg-reconfigureseems to be the right option.
– Melebius
Oct 5 '16 at 12:17
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:sudo apt-get install linux-headers-`uname -r`thensudo dpkg-reconfigure virtualbox-dkmsand finallysudo dpkg-reconfigure virtualbox
– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
1
1
Wonder why “an other way” is mentioned before the “normal” one. However,
dpkg-reconfigure seems to be the right option.– Melebius
Oct 5 '16 at 12:17
Wonder why “an other way” is mentioned before the “normal” one. However,
dpkg-reconfigure seems to be the right option.– Melebius
Oct 5 '16 at 12:17
1
1
To add to this, I found the following sequence worked when I unpgraded to 16.04:
sudo apt-get install linux-headers-`uname -r` then sudo dpkg-reconfigure virtualbox-dkms and finally sudo dpkg-reconfigure virtualbox– Dave
Feb 20 '17 at 13:48
To add to this, I found the following sequence worked when I unpgraded to 16.04:
sudo apt-get install linux-headers-`uname -r` then sudo dpkg-reconfigure virtualbox-dkms and finally sudo dpkg-reconfigure virtualbox– Dave
Feb 20 '17 at 13:48
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
This will put you in the OPs situation (again) each kernel update.
– earthmeLon
3 hours ago
add a comment |
You need the kernel header as well. Based on your output, sudo apt-get install kernel-headers-3.5.0-17-generic should do it. On the guest VM, either autorun the ISO image or sudo sh ./VBoxLinuxAdditions.run from the shell prompt should work. Appears this is a known problem with the latest 12.10 release.
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
add a comment |
You need the kernel header as well. Based on your output, sudo apt-get install kernel-headers-3.5.0-17-generic should do it. On the guest VM, either autorun the ISO image or sudo sh ./VBoxLinuxAdditions.run from the shell prompt should work. Appears this is a known problem with the latest 12.10 release.
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
add a comment |
You need the kernel header as well. Based on your output, sudo apt-get install kernel-headers-3.5.0-17-generic should do it. On the guest VM, either autorun the ISO image or sudo sh ./VBoxLinuxAdditions.run from the shell prompt should work. Appears this is a known problem with the latest 12.10 release.
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
You need the kernel header as well. Based on your output, sudo apt-get install kernel-headers-3.5.0-17-generic should do it. On the guest VM, either autorun the ISO image or sudo sh ./VBoxLinuxAdditions.run from the shell prompt should work. Appears this is a known problem with the latest 12.10 release.
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
answered Oct 21 '12 at 18:50
cogitoergosumcogitoergosum
33113
33113
add a comment |
add a comment |
Didn't work for me. Solved it by running:
gksudo synaptic
Search for 'dkms' and (re)install the one for VirtualBox and press the 'Apply' button. The output should say that virtualbox kernel drivers are up and running.
edited Jul 17 '15 at 0:36
simplify
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
add a comment |
Didn't work for me. Solved it by running:
gksudo synaptic
Search for 'dkms' and (re)install the one for VirtualBox and press the 'Apply' button. The output should say that virtualbox kernel drivers are up and running.
edited Jul 17 '15 at 0:36
simplify
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
add a comment |
Didn't work for me. Solved it by running:
gksudo synaptic
Search for 'dkms' and (re)install the one for VirtualBox and press the 'Apply' button. The output should say that virtualbox kernel drivers are up and running.
edited Jul 17 '15 at 0:36
simplify
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
Didn't work for me. Solved it by running:
gksudo synaptic
Search for 'dkms' and (re)install the one for VirtualBox and press the 'Apply' button. The output should say that virtualbox kernel drivers are up and running.
edited Jul 17 '15 at 0:36
simplify
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
edited Jul 17 '15 at 0:36
simplify
74
edited Jul 17 '15 at 0:36
simplify
74
edited Jul 17 '15 at 0:36
simplify
74
74
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
answered Dec 18 '12 at 20:25
Donald DominkoDonald Dominko
211
211
add a comment |
add a comment |
This is caused by the kernel headers not being available. These headers are not typically required, but help other applications need them to build kernel modules to keep in sync with your distribution and the version you are using.
You can install specific headers, or you can install 'generic', or 'current':
sudo apt install linux-headers-generic
This will ensure that when you take in new kernels, the headers of those kernels are also installed. When you update your kernel, VirtualBox will be able to update itself with the newest, matching headers. Sometimes these can be found by other names, such as linux-headers-amd64, in other distributions.
After you have the headers, you can purge/re-install VirtualBox, or have VirtualBox rebuild the modules and complete the setup:
sudo dpkg-reconfigure virtualbox-dkms
sudo modprobe vboxdrv
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
add a comment |
This is caused by the kernel headers not being available. These headers are not typically required, but help other applications need them to build kernel modules to keep in sync with your distribution and the version you are using.
You can install specific headers, or you can install 'generic', or 'current':
sudo apt install linux-headers-generic
This will ensure that when you take in new kernels, the headers of those kernels are also installed. When you update your kernel, VirtualBox will be able to update itself with the newest, matching headers. Sometimes these can be found by other names, such as linux-headers-amd64, in other distributions.
After you have the headers, you can purge/re-install VirtualBox, or have VirtualBox rebuild the modules and complete the setup:
sudo dpkg-reconfigure virtualbox-dkms
sudo modprobe vboxdrv
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
add a comment |
This is caused by the kernel headers not being available. These headers are not typically required, but help other applications need them to build kernel modules to keep in sync with your distribution and the version you are using.
You can install specific headers, or you can install 'generic', or 'current':
sudo apt install linux-headers-generic
This will ensure that when you take in new kernels, the headers of those kernels are also installed. When you update your kernel, VirtualBox will be able to update itself with the newest, matching headers. Sometimes these can be found by other names, such as linux-headers-amd64, in other distributions.
After you have the headers, you can purge/re-install VirtualBox, or have VirtualBox rebuild the modules and complete the setup:
sudo dpkg-reconfigure virtualbox-dkms
sudo modprobe vboxdrv
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
This is caused by the kernel headers not being available. These headers are not typically required, but help other applications need them to build kernel modules to keep in sync with your distribution and the version you are using.
You can install specific headers, or you can install 'generic', or 'current':
sudo apt install linux-headers-generic
This will ensure that when you take in new kernels, the headers of those kernels are also installed. When you update your kernel, VirtualBox will be able to update itself with the newest, matching headers. Sometimes these can be found by other names, such as linux-headers-amd64, in other distributions.
After you have the headers, you can purge/re-install VirtualBox, or have VirtualBox rebuild the modules and complete the setup:
sudo dpkg-reconfigure virtualbox-dkms
sudo modprobe vboxdrv
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
edited 3 hours ago
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
answered 3 hours ago
earthmeLonearthmeLon
6,4331851
6,4331851
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f203586%2fhow-do-i-install-the-virtualbox-dkms-package%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
