Hi, Le dimanche 12 janvier 2025 à 15:33 +0200, Roman Riabenko a écrit : >
> Debian maintainers rejected a request to set the option in the past: > https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=924794 > > I downloaded the current Debian kernels from the stable release > (Bookworm) and Sid and checked that it does not have the option set. > > Instead, Fedora has the option set to disable this backend by > default: > https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel-x86_64-fedora.config#_2098 > > Arch Linux has a similar issue report undecided: > https://bugs.archlinux.org/task/70140 > > It appears, that the objective of introducing the option was > to maintain the existing behaviour but allow the user to > override it on problematic hardware: > https://lore.kernel.org/lkml/20130312211417.GC16558@thinkpad-t410/ > > It looks like there are some advantages and disadvantages to setting > the option. The difference seems to be in distributions' approaches > to what they think their users would want. > > 1. The default is to enable the backend so that the users can > troubleshoot kernel issues. Turning the backend off is considered > optional for faulty UEFI implementations. > > 2. Instead, some distributions want to limit writing to EFI variables > to > prevent issues with faulty UEFI implementations from happening at > all. > > What kind of distribution is Guix System? Maybe a third option of not > trusting the proprietary UEFI? > > Kind regards > Roman Since the solution seems to take time to find, and since the temporary solution of deleting the “dump” files on my device /sys/firmware/efi/efivars doesn't work, I'm going to reinstall my system before I get stuck on an unfortunate reboot. Would you advise me to use legacy mode for booting (instead of efi) to avoid this problem again in the near future? Christophe
