Am 30.09.20 um 18:45 schrieb Stephen John Smoogen:
>
> 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. 

I have replaced the files grubia32.efi and grubx64.efi  in
ANADCONDA:/EFI/BOOT/ with the ones from the F31 image.

After 2 tries, the surface pro 4 booted like a charm.

@Elmar: can you confirm this for your surface device?


Sidenote: the files on the iso9660 partition are unchanged (because it
mounts obviously ro )

best regards,
Marius

PS: I'm really excited to make an iso, that boots into a working surface
kernel with touch enabled etc. . Unfortunatly, that kernel isn't fedora
complient  license wise :(
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to