On Wed, Sep 30, 2020 at 12:45:40PM -0400, Stephen John Smoogen wrote: > The Fedora secure boot signing keys were updated after F32 was initially > released to deal with the grub2 problems found during the summer. I believe > some systems have needed firmware updates from the manufacturer to work > with the new key because they worked by white listing the old set, and > don't know how to handle when a new key signed and authorized is presented. > I don't know how the Surface Pro does its firmware updates and if one is > needed. This would be my guess as well. If you install with secure boot disabled and then turn it back on after doing a full update does it boot correctly? Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
