On trying to boot the above kernel, I get a "Failed to start Load Kernel Modules" error. This appears to be caused by missing vboxdrv modules (from VirtualBox). Booting an earlier kernel works fine.
Two comments:
1) I thought DKMS was supposed to rebuild the VBox modules for each new kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
2) The error message was unhelpful as it didn't identify which modules failed. It took some searching to find what the problem was. Surely this could be done better. (In fact I'd argue that failing to load these modules shouldn't result in a failed boot, but I realize that's maybe harder to deal with).
poc
On 06/11/14 20:43, Patrick O'Callaghan wrote:
On trying to boot the above kernel, I get a "Failed to start Load Kernel Modules" error. This appears to be caused by missing vboxdrv modules (from VirtualBox). Booting an earlier kernel works fine.
Yes. And mine have built just fine.
/usr/lib/modules/3.14.5-200.fc20.x86_64/extra/vboxdrv.ko
Two comments:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
Run dkms manually?
- The error message was unhelpful as it didn't identify which modules
failed. It took some searching to find what the problem was. Surely this could be done better. (In fact I'd argue that failing to load these modules shouldn't result in a failed boot, but I realize that's maybe harder to deal with).
I've not run into this problem.
On 06/11/14 20:43, Patrick O'Callaghan wrote:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
Oh....and BTW you may want to check....
/var/lib/dkms/vboxhost/4.3.12/3.14.5-200.fc20.x86_64/x86_64/log/make.log
On 06/11/2014 08:43 AM, Patrick O'Callaghan wrote:
On trying to boot the above kernel, I get a "Failed to start Load Kernel Modules" error. This appears to be caused by missing vboxdrv modules (from VirtualBox). Booting an earlier kernel works fine.
I have virtualbox installed and I also have that kernel. I just rebooted this morning, so I know it works, and I just ran virtual box. It is showing 4.3.12r93733 uname -a Linux pauls-server 3.14.5-200.fc20.x86_64 #1 SMP Mon Jun 2 14:26:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Two comments:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
- The error message was unhelpful as it didn't identify which modules
failed. It took some searching to find what the problem was. Surely this could be done better. (In fact I'd argue that failing to load these modules shouldn't result in a failed boot, but I realize that's maybe harder to deal with).
poc
On Jun 11, 2014 6:13 PM, "Patrick O'Callaghan" pocallaghan@gmail.com wrote:
On trying to boot the above kernel, I get a "Failed to start Load Kernel Modules" error. This appears to be caused by missing vboxdrv modules (from VirtualBox). Booting an earlier kernel works fine.
Two comments:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
- The error message was unhelpful as it didn't identify which modules
failed. It took some searching to find what the problem was. Surely this could be done better. (In fact I'd argue that failing to load these modules shouldn't result in a failed boot, but I realize that's maybe harder to deal with).
poc
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Do you have RPMFusions's VB or the one from Oracle's repo? I found RPMFusion's build problematic as they provide modules through kmod. Akmod can automatically build modules for you.
So I have switched to Oracle's version. It comes with /etc/init.d/vboxdrv that you could run manually to build the modules using following command.
/etc/init.d/vboxdrv setup
-Sudhir.
On Wed, 2014-06-11 at 21:11 +0800, Ed Greshko wrote:
On 06/11/14 20:43, Patrick O'Callaghan wrote:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
Oh....and BTW you may want to check....
/var/lib/dkms/vboxhost/4.3.12/3.14.5-200.fc20.x86_64/x86_64/log/make.log
There's nothing in /var/lib/dkms except a short text file.
poc
On Wed, 2014-06-11 at 20:01 +0530, Sudhir Khanger wrote:
Do you have RPMFusions's VB or the one from Oracle's repo? I found RPMFusion's build problematic as they provide modules through kmod. Akmod can automatically build modules for you.
So I have switched to Oracle's version. It comes with /etc/init.d/vboxdrv that you could run manually to build the modules using following command.
/etc/init.d/vboxdrv setup
I have the RPMfusion one. I'll remove it and try the Oracle one, thanks.
poc
On Wed, 2014-06-11 at 16:40 +0100, Patrick O'Callaghan wrote:
On Wed, 2014-06-11 at 20:01 +0530, Sudhir Khanger wrote:
Do you have RPMFusions's VB or the one from Oracle's repo? I found RPMFusion's build problematic as they provide modules through kmod. Akmod can automatically build modules for you.
So I have switched to Oracle's version. It comes with /etc/init.d/vboxdrv that you could run manually to build the modules using following command.
/etc/init.d/vboxdrv setup
I have the RPMfusion one. I'll remove it and try the Oracle one, thanks.
That did the trick. Thanks again.
I'll complain about the obscure error message on BZ.
poc
On 06/11/14 23:39, Patrick O'Callaghan wrote:
On Wed, 2014-06-11 at 21:11 +0800, Ed Greshko wrote:
On 06/11/14 20:43, Patrick O'Callaghan wrote:
- I thought DKMS was supposed to rebuild the VBox modules for each new
kernel automatically. This has happened in the past but seems to have failed now. Why would this be and how can I fix it?
Oh....and BTW you may want to check....
/var/lib/dkms/vboxhost/4.3.12/3.14.5-200.fc20.x86_64/x86_64/log/make.log
There's nothing in /var/lib/dkms except a short text file.
OK.... I forgot about the RPMFusion provided packages. I use the Oracle supplied packages and they build the modules via dkms and the log exists.
On 11/06/14 18:40, Patrick O'Callaghan wrote:
On Wed, 2014-06-11 at 20:01 +0530, Sudhir Khanger wrote:
Do you have RPMFusions's VB or the one from Oracle's repo? I found RPMFusion's build problematic as they provide modules through kmod. Akmod can automatically build modules for you.
So I have switched to Oracle's version. It comes with /etc/init.d/vboxdrv that you could run manually to build the modules using following command.
/etc/init.d/vboxdrv setup
I have the RPMfusion one. I'll remove it and try the Oracle one, thanks.
poc
AFAICS, the RpmFusion package uses akmod not DKMS to build the kernel module(s).
With kmod you have two options either install kmod-VirtualBox which has pre-built kernel modules in which case you'll have to wait for the package to get updated to get the modules for the updated kernel; or install akmod-VirtualBox which should build the module at boot, of course the build can fail and require a patch... etc.
On Fri, Jun 13, 2014 at 9:16 PM, Ahmad Samir ahmadsamir3891@gmail.com wrote:
On 11/06/14 18:40, Patrick O'Callaghan wrote:
On Wed, 2014-06-11 at 20:01 +0530, Sudhir Khanger wrote:
Do you have RPMFusions's VB or the one from Oracle's repo? I found RPMFusion's build problematic as they provide modules through kmod. Akmod can automatically build modules for you.
So I have switched to Oracle's version. It comes with /etc/init.d/vboxdrv that you could run manually to build the modules using following command.
/etc/init.d/vboxdrv setup
I have the RPMfusion one. I'll remove it and try the Oracle one, thanks.
poc
AFAICS, the RpmFusion package uses akmod not DKMS to build the kernel module(s).
With kmod you have two options either install kmod-VirtualBox which has pre-built kernel modules in which case you'll have to wait for the package to get updated to get the modules for the updated kernel; or install akmod-VirtualBox which should build the module at boot, of course the build can fail and require a patch... etc.
-- Ahmad Samir
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
I haven't had any problems with the Oracle supplied VirtualBox for a few months. The one from RPMFusion kept lagging behind; yum would upgrade to latest kernel irrespective of if VirtualBox's dependencies are met or not.
On 13/06/14 18:57, Sudhir Khanger wrote:
On Fri, Jun 13, 2014 at 9:16 PM, Ahmad Samir ahmadsamir3891@gmail.com wrote:
AFAICS, the RpmFusion package uses akmod not DKMS to build the kernel module(s).
With kmod you have two options either install kmod-VirtualBox which has pre-built kernel modules in which case you'll have to wait for the package to get updated to get the modules for the updated kernel; or install akmod-VirtualBox which should build the module at boot, of course the build can fail and require a patch... etc.
-- Ahmad Samir
I haven't had any problems with the Oracle supplied VirtualBox for a few months. The one from RPMFusion kept lagging behind; yum would upgrade to latest kernel irrespective of if VirtualBox's dependencies are met or not.
I am not with or against using the package from upstream; but you could remove kmod-VirtualBox and install akmod-VirtualBox and that one doesn't depend of a specific kernel version as it's supposed to build the kernel modules automatically for a new kernel.
On Fri, Jun 13, 2014 at 9:30 PM, Ahmad Samir ahmadsamir3891@gmail.com wrote:
On 13/06/14 18:57, Sudhir Khanger wrote:
On Fri, Jun 13, 2014 at 9:16 PM, Ahmad Samir ahmadsamir3891@gmail.com wrote:
AFAICS, the RpmFusion package uses akmod not DKMS to build the kernel module(s).
With kmod you have two options either install kmod-VirtualBox which has pre-built kernel modules in which case you'll have to wait for the package to get updated to get the modules for the updated kernel; or install akmod-VirtualBox which should build the module at boot, of course the build can fail and require a patch... etc.
-- Ahmad Samir
I haven't had any problems with the Oracle supplied VirtualBox for a few months. The one from RPMFusion kept lagging behind; yum would upgrade to latest kernel irrespective of if VirtualBox's dependencies are met or not.
I am not with or against using the package from upstream; but you could remove kmod-VirtualBox and install akmod-VirtualBox and that one doesn't depend of a specific kernel version as it's supposed to build the kernel modules automatically for a new kernel.
-- Ahmad Samir -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Sorry but my experience is that akmod keeps failing to build modules for the latest kernel.
On 13/06/14 19:08, Sudhir Khanger wrote:
On Fri, Jun 13, 2014 at 9:30 PM, Ahmad Samir ahmadsamir3891@gmail.com wrote:
I am not with or against using the package from upstream; but you could remove kmod-VirtualBox and install akmod-VirtualBox and that one doesn't depend of a specific kernel version as it's supposed to build the kernel modules automatically for a new kernel.
-- Ahmad Samir
Sorry but my experience is that akmod keeps failing to build modules for the latest kernel.
Building the module with akmod could fail due to a problem on your system or simply because the kernel modules fail to build with the newer kernel, which means that it would fail to build with DKMS with the upstream package too. (IIUC akmod and DKMS are two ways to build the kernel module(s), different ways but the same end goal).
-
Ahmad Samir -
Ed Greshko -
Patrick O'Callaghan -
Paul Cartwright -
Sudhir Khanger