* A post early this year within this MX Linux forum where @hamak reported about "Acer ES1-132 No Bootable Device" viewtopic.php?f=107&t=62554
* Another post by a user "spektro37" within an Acer forum, where this was mentioned a bit earlier
https://community.acer.com/en/discussio ... ent_490737
* An even earlier post in Russian
https://www.linux.org.ru/forum/linux-i ... d=13169511
by user V1KT0P, who wrote:
which translates into English using DeepL.com:В общем нашел причину того что невозможно загрузиться. Все дело в рукожопии тех кто писал UEFI прошивку. Эти *удаки не нашли ничего лучшего чем захардкорить пути по которым возможен запуск, я вытянул из прошивки вот такие данные:
In general, I found the reason why it is impossible to boot. It's all about the handiwork of those who wrote the UEFI firmware. These *mistakes* couldn't find anything better than to hardcode the paths that can be used for startup, so I pulled these data out of the firmware:
and shows this list of hardcoded entries within the readonly NVRAM:
Code: Select all
\EFI\Linux\BOOTX64.efi (Linux)
\EFI\Microsoft\Boot\bootmgfw.efi (Windows Boot Manager)
\EFI\ubuntu\shim.efi (ubuntu SECURE)
\EFI\ubuntu\shim$cpu$.efi (ubuntu SECURE)
\EFI\ubuntu\grub.efi (ubuntu NORMAL)
\EFI\fedora\shim.efi (Fedora)
\EFI\android\bootx64.efi (Android)
\EFI\opensuse\grubx64.efi (topenSUSE)
\EFI\redhat\grub.efi (Red Hat Linux)
\EFI\SuSE\elilo.efi (SuSE Linux)
\EFI\ubuntu\grub$cpu$.efi (ubuntu NORMAL)
