| Summary: | Mageia-9-alpha1-x86_64.iso : grub2-install failed : EFI variables are not supported on this system : efibootmgr failed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | PC LX <mageia> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | release_blocker | CC: | bequimao.de, contact, ftg, mageia |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-stage2 | CVE: | |
| Status comment: | fixed in drakx-installer-stage2-18.51 | ||
| Attachments: |
Install report.
Screen shot of error messages. |
||
|
Description
PC LX
2022-10-23 01:11:41 CEST
Created attachment 13438 [details]
Install report.
Created attachment 13439 [details]
Screen shot of error messages.
This occurs because the Linux 6.0 kernel has removed the old and deprecated interface to the EFI variables which was previously found at /sys/firmware/efi/vars. The new way to access the EFI variables is to mount the efivarfs filesystem at /sys/firmware/efi/efivars, but this is not done by the installer. The temporary workaround is to wait until the installer reaches the Summary screen, then switch to the debug console by pressing Ctrl-Alt-F2 (or emulating that key press if you are using QEMU), entering the command mount -t efivarfs none /mnt/sys/firmware/efi/efivars then switching back to the installer GUI by pressing Ctrl-Alt-F7 and continuing with the installation. CC:
(none) =>
mageia Interestingly it might/should work if you choose refind as bootloader as that already checks for efivars being mounted :) ah, its part of write_refind_previous_boot_var(), so need more work. I guess we should factor out that checking/mounting/unmounting efivarfs and hook it into needed places... (In reply to Martin Whitaker from comment #3) > This occurs because the Linux 6.0 kernel has removed the old and deprecated > interface to the EFI variables which was previously found at > /sys/firmware/efi/vars. The new way to access the EFI variables is to mount > the efivarfs filesystem at /sys/firmware/efi/efivars, but this is not done > by the installer. > > The temporary workaround is to wait until the installer reaches the Summary > screen, then switch to the debug console by pressing Ctrl-Alt-F2 (or > emulating that key press if you are using QEMU), entering the command > > mount -t efivarfs none /mnt/sys/firmware/efi/efivars > > then switching back to the installer GUI by pressing Ctrl-Alt-F7 and > continuing with the installation. When I do this I get the following error during bootloader installation: Error: <Installing for x86_64-efi platform. Could not prepare Boot variable: Function not implemented grub2-install: error: efibootmgr failed to register the boot entry: input/output error ...propagated at /usr/lib/libDrakX/any.pm line 278 CC:
(none) =>
ftg (In reply to Frank Griffin from comment #6) > When I do this I get the following error during bootloader installation: > > Error: <Installing for x86_64-efi platform. > Could not prepare Boot variable: Function not implemented > grub2-install: error: efibootmgr failed to register the boot entry: > input/output error > ...propagated at /usr/lib/libDrakX/any.pm line 278 That would appear to be a different issue. Best open a new bug report for that.
Martin Whitaker
2022-10-24 23:18:41 CEST
Status comment:
(none) =>
fix added in git
Ulrich Beckmann
2022-10-25 13:58:02 CEST
CC:
(none) =>
bequimao.de (In reply to Martin Whitaker from comment #3) > mount -t efivarfs none /mnt/sys/firmware/efi/efivars That command solved the issue. The installation completed correctly and the system booted to a working Plasma desktop, after entering the username/password. Thanks. I confirm the bug on Mageia9-alpha1 iso when installing on efi x86_64 system CC:
(none) =>
contact The fix will be include in the next ISO build. Status comment:
fix added in git =>
fixed in drakx-installer-stage2-18.51 This was fixed in the second round of alpha1 ISOs, dated Sat Oct 29 07:52:30 PM CEST 2022. I have just retested and confirmed the fix. Resolution:
(none) =>
FIXED |