On Wed, Feb 03, 2021 at 11:53:04AM -0800, Paolo Galtieri wrote: > > Jorge, > thank you for the information, however, since there is a good reason to > have secure boot enabled and since Fedora 33 boots with it enabled I would > like to find a solution that does not require this. Additionally this > system boots to Windows so I really don't want to mess around with issues > booting Windows. The only alternative is to sign the kernel modules with your own certificate, and load that certificate into the firmware as a valid Secure Boot CA. https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/#sect-signing-kernel-modules-for-secure-boot -- Jonathan Billings <billings@xxxxxxxxxx> _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
