Once upon a time, stan via users <users@xxxxxxxxxxxxxxxxxxxxxxx> said: > On Tue, 11 Jun 2019 08:39:12 -0700 > stan <upaitag@xxxxxxxx> wrote: > > 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. The UEFI standard defines its own filesystem format that is a fixed subset of FAT32. Only ASCII and UCS-2 character encodings are officially supported for long filename support. Windows FAT32 includes UTF-16 for LFN, but that's not supported in UEFI (UTF-8 is not even mentioned). -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ 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
