Kernel 3.14.5-200.fc20.x86_64 won't boot: module problem

[Sudhir Khanger]

On Fri, Jun 13, 2014 at 9:30 PM, Ahmad Samir <ahmadsamir3891 at gmail.com> wrote:
> On 13/06/14 18:57, Sudhir Khanger wrote:
>>
>> On Fri, Jun 13, 2014 at 9:16 PM, Ahmad Samir <ahmadsamir3891 at 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 at 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.

-- 
Regards,
Sudhir Khanger.
sudhirkhanger.com
https://github.com/donniezazen