After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
-------- Uninstall Beginning -------- Module: vboxhost Version: 4.2.16 Kernel: 3.10.6-200.fc19.x86_64 (x86_64) -------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel. Removing any linked weak-modules
vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version.
vboxpci.ko: - Uninstallation - Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version.
depmod.....
DKMS: uninstall completed.
On Tue, Sep 03, 2013 at 04:10:15AM -0400, Bob Goodwin ~ Zuni, Virginia, USA wrote:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Virtualbox needs a kernel module, since the module is out-of-tree, you needed dkms to compile it for every new kernel update. If you do not use any other software that needs this facility, you can safely ignore it.
Hope this helps,
03.09.2013 10:10, Bob Goodwin ~ Zuni, Virginia, USA:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
[...]
Your "yum update" probably did remove kernel 3.10.6-200.fc19.x86_64. Therefore, it's a good thing, that dkms removes the (now useless) VirtualBox-modules which were built for this kernel version.
On 03/09/13 04:25, Markus Schönhaber wrote:
03.09.2013 10:10, Bob Goodwin ~ Zuni, Virginia, USA:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
[...]
Your "yum update" probably did remove kernel 3.10.6-200.fc19.x86_64. Therefore, it's a good thing, that dkms removes the (now useless) VirtualBox-modules which were built for this kernel version.
Ok, I will ignore it then and see what happens when next I run vbox.
Thanks all.
Bob
2013-09-03 10:29, Bob Goodwin ~ Zuni, Virginia, USA skrev:
On 03/09/13 04:25, Markus Schönhaber wrote:
03.09.2013 10:10, Bob Goodwin ~ Zuni, Virginia, USA:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
[...]
Your "yum update" probably did remove kernel 3.10.6-200.fc19.x86_64. Therefore, it's a good thing, that dkms removes the (now useless) VirtualBox-modules which were built for this kernel version.
Ok, I will ignore it then and see what happens when next I run vbox.
You should do following:
$ sudo /etc/init.d/vboxdrv setup
Thanks all.
Bob
On 03/09/13 04:43, Jon Ingason wrote:
2013-09-03 10:29, Bob Goodwin ~ Zuni, Virginia, USA skrev:
On 03/09/13 04:25, Markus Schönhaber wrote:
03.09.2013 10:10, Bob Goodwin ~ Zuni, Virginia, USA:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
[...]
Your "yum update" probably did remove kernel 3.10.6-200.fc19.x86_64. Therefore, it's a good thing, that dkms removes the (now useless) VirtualBox-modules which were built for this kernel version.
Ok, I will ignore it then and see what happens when next I run vbox.
You should do following:
$ sudo /etc/init.d/vboxdrv setup
Thanks all.
Bob
Will do, thank you.
Bob Goodwin ~ Zuni, Virginia, USA <bobgoodwin <at> wildblue.net> writes:
After"yum update" this morning I have this notice. I recall needing dkms for some reason after installing vbox but don't recall the reason for it. I assume there is some action required on my part but what? It seems easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
It did exactly what it was supposed to. By installing dkms, the host will automatically build the kernel modules for each kernel when installing it, and remove them (which is what you saw) when uninstalling it. You can see the currently installed kernel modules with the command "dkms status". You should have a vboxhost entry corresponding to each installed kernel, similar to this:
vboxhost, 4.2.16, 3.10.10-200.fc19.x86_64, x86_64: installed vboxhost, 4.2.16, 3.10.7-200.fc19.x86_64, x86_64: installed vboxhost, 4.2.16, 3.10.9-200.fc19.x86_64, x86_64: installed
On 03/09/13 06:51, Andre Robatino wrote:
What command do I need to execute to fix this or should I just forget dkms?
It did exactly what it was supposed to. By installing dkms, the host will automatically build the kernel modules for each kernel when installing it, and remove them (which is what you saw) when uninstalling it. You can see the currently installed kernel modules with the command "dkms status". You should have a vboxhost entry corresponding to each installed kernel, similar to this:
vboxhost, 4.2.16, 3.10.10-200.fc19.x86_64, x86_64: installed vboxhost, 4.2.16, 3.10.7-200.fc19.x86_64, x86_64: installed vboxhost, 4.2.16, 3.10.9-200.fc19.x86_64, x86_64: installed
Well, not exactly but perhaps this is an indication of success:
/var/lib/dkms/vboxhost/kernel-3.10.10-200.fc19.x86_64-x86_64 /var/lib/dkms/vboxhost/kernel-3.10.7-200.fc19.x86_64-x86_64 /var/lib/dkms/vboxhost/kernel-3.10.9-200.fc19.x86_64-x86_64 /var/lib/dkms/vboxhost/4.2.16/3.10.10-200.fc19.x86_64 /var/lib/dkms/vboxhost/4.2.16/3.10.7-200.fc19.x86_64 /var/lib/dkms/vboxhost/4.2.16/3.10.9-200.fc19.x86_64
Thanks for the explanation,
Bob
-
Andre Robatino -
Bob Goodwin -
Jon Ingason -
Markus Schönhaber -
Suvayu Ali