2017-02-28 14:20 GMT-06:00 Andrew Lofthouse :
>
>>
>> >
>> > With the last system update I have seem a message in system start up
>> > about a error loading kernel modules, after that VirtualBox do not
>> > start because the apropiate module can not been loaded.
>> >
>> > https://bugzilla.redhat.co
You did not menthon what copy of VirtualBox you used, and that makes a
difference.
I have been running the copy from rpmfusion for some time, and
experienced the same trouble you had. It often breaks after
updates/upgrades, forcing me to use old kernel copies.
In the end I decided to fall back to
Thanks a lot for the feedback!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
> >
> > With the last system update I have seem a message in system start up
> > about a error loading kernel modules, after that VirtualBox do not
> > start because the apropiate module can not been loaded.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1426836
> >
> > There is another repo
On Tue, 28 Feb 2017 12:54:22 -0600
William Moreno wrote:
> Hello
>
> With the last system update I have seem a message in system start up
> about a error loading kernel modules, after that VirtualBox do not
> start because the apropiate module can not been loaded.
>
> https://bugzilla.redhat.co
Hello
With the last system update I have seem a message in system start up about
a error loading kernel modules, after that VirtualBox do not start because
the apropiate module can not been loaded.
https://bugzilla.redhat.com/show_bug.cgi?id=1426836
There is another report about VirtualBox not r
