On Tue, 11 Jun 2019 08:39:12 -0700 stan <upaitag@xxxxxxxx> wrote: > The solution is that the kernel is already signed by the build > process, when it is built from the Fedora kernel spec. The problem This signature is the problem, as it is a red hat signature and has to be removed. That was the other part of the solution. > wasn't the signing, it was a missing code page for 8859-1. This is > the default code page for vfat in the kernel, so it couldn't read > the /boot/efi partition. Once I added the code page, the boot > succeeds as UEFI. I'm going to try changing that default to utf-8 > so I don't have to keep the 8859-1 code page. The code page was a legitimate issue, but only part of the issue. When I tried utf-8 for the /boot/efi partition booting failed. There must be some hardcoded linking of vfat and ISO8859 somewhere. I don't think there is a technical reason precluding the use of utf-8 with vfat. For the process that actually worked to yield a signed custom kernel, see additional information in https://bugzilla.redhat.com/show_bug.cgi?id=1719930 _______________________________________________ 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
