| Summary: | Mageia 9 installation fail during grub2 setup due to failure to write to EFI NVRAM | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Cyril Levet <cyril.levet0780> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | NEW --- | QA Contact: | |
| Severity: | critical | ||
| Priority: | High | CC: | mageia, mageia |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.mageia.org/show_bug.cgi?id=31403 | ||
| Whiteboard: | |||
| Source RPM: | kernel-6.4.3-1.mga9 | CVE: | |
| Status comment: | |||
|
Description
Cyril Levet
2023-07-23 17:54:58 CEST
Cyril Levet
2023-07-23 17:55:34 CEST
Priority:
Normal =>
High I set to release_blocker as it is a regression from mga8. Martin do you think you can take a look to this ? CC:
(none) =>
mageia The error message indicates that efibootmgr could not add a new entry in the EFI non-volatile RAM. What is the output from /sbin/efibootmgr when booting from the Live ISO? CC:
(none) =>
mageia /sbin/efibootmgr BootCurrent: 0005 Timeout: 2 seconds BootOrder: 0003,0002,0004,0005 Boot0002* Windows Boot Manager HD(2,GPT,7daa84fc-b1aa-4626-9a66-31ea054c3866,0xfa000,0x31800)/File(\EFI\Micro soft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390 064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d0066003300320062003 30034003400640034003700390035007d0000006f000100000010000000040000007fff0400 Boot0003* Hard Drive BBS(HD,,0x0) Boot0004* CD/DVD Drive BBS(CDROM,,0x0) Boot0005* UEFI: SMI USB DISK 1100 PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(3,0)/HD(1,MBR,0x0,0x785134,0x2 000) For information, Windows is no longer installed since several years but the entre for Windows Boot manager is still here. Again using the Live ISO, run the following command as root efibootmgr -c Does that add a new boot entry, or fail with the same error reported when installing GRUB? That entry is unlikely to work as it will have default values for everything. You can delete it by efibootmgr -b 1 -B assuming the new entry was Boot0001 (it might be a different number). Similarly you could delete the Windows entry by efibootmgr -b 2 -B If it doesn't work, could you try the same thing with a Mageia 8 Live ISO. Neither efibootmgr -c or efibootmgr -b 2 -B works. The same message is displayed each time : No space left on device. efibootmgr -c works with the Mageia 8 Live ISO. It creates a Boot0000* Linux Another strange behaviour, when I try to delete Windows entry with Mageia 9 Live ISO, it tells me that it is impossible because No space left on device. However, when I reboot on the Mageia 8 Live, the Windows entry has disappeared. I think this is either a bug in the efivarfs pseudo-filesystem or a BIOS bug that the kernel previously ignored. Assigning to the kernel/drivers team. The workaround is to select the "Install in /EFI/BOOT" option when configuring GRUB at the end of installation. That causes GRUB to be installed in the EFI fallback location, which means it doesn't need to add an entry in the NVRAM. Component:
Installer =>
RPM Packages When selecting the option "Install in /EFI/BOOT" I can finish the installation, but I don't know how to boot on Mageia after. I haven't any proper options at startup. It's ok. I found how to do it in the BIOS. This old ASUS BIOS is not really user-friendly.
Nicolas Lécureuil
2023-07-25 19:40:31 CEST
Priority:
release_blocker =>
High
Martin Whitaker
2023-08-25 10:13:46 CEST
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=31403 |