Hello I remind you that at startup, the EFI computer is not in SECURE mode. There is therefore no reason to require that the secure mode be installed.
There is an installation option --n0-nvram Use it! It is easy to do a read command of the NVRAM to see that it is refused in reading. This implies that writing will probably not be possible! You could even set the noefi option in the options of the /etc/default/grub file !!! Thank you for improving the situation. This attached file contains the boot-repair trace with the content of dmesg trace ** Attachment added: "Page fault caused by firmware at PA: 0x660591d0" https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914599/+attachment/5459956/+files/Boot-Repair.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914599 Title: efi: Froze efi_rts_wq and disabled EFI Runtime Services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs