On 08/05/18 01:12, Sudhir Khanger wrote: > Like I mentioned earlier that systemd-modules-load.service service fails and starts > working after I create a new initramfs. You were unwilling to accept what I > experienced on my system irrespective of the cause I shot a video of it which you > can find below. I'm not unwilling, just telling you that it isn't related to your initial assumption that it has to do with VirtualBox Modules as those aren't needed in the initramfs are aren't loaded by systemd-modules-load.service. As I pointed out, systemd-modules-load.service is triggered by certain conditions. One of them is... ConditionDirectoryNotEmpty=|/etc/modules-load.d And you've answered that in your follow up to another query.... $ cat /etc/modules-load.d/bbswitch.conf # Load bbswitch.ko at boot bbswitch So, the systemd-modules-load.service failure is due to "bbswitch" not being available. I don't know anything about how you've installed bumblebee or how it manages the building of a kernel matching module. But that is the area you should be investigating and not anything to do with Virtualbox. -- Conjecture is just a conclusion based on incomplete information. It isn't a fact.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/SKEGX7ZBIQ63RSAGNSGA7277J5NSCSOI/
