Description of problem: After reinstalling grub2-efi, system failed to boot. Culprit is that efibootmgr failed to write EFI variables so entries can be deleted but not added and sometimes updated. To fix this you must use EFI/BIOS to add bootloader again which is nontrivial for users. Device: ASUS VivoBook S551LB.207 dmesg snippet: [56413.895611] efivars: set_variable() failed: status=8000000000000009 [56421.781446] efivars: set_variable() failed: status=8000000000000009 [56452.410021] efivars: set_variable() failed: status=8000000000000009 This bug is fixed by kernel commit 31ff2f20d9003e74991d135f56e503fe776c127c Author: Matthew Garrett <email address hidden> Date: Mon Apr 15 13:09:47 2013 -0700 efi: Distinguish between "remaining space" and actually used space See also: http://thread.gmane.org/gmane.linux.kernel.efi/1081 Version-Release number of selected component (if applicable): kernel-desktop-3.8.13.4-desktop-1.mga3 How reproducible: Always Steps to Reproduce: 1. run efibootmgr RESULT: BootCurrent: 0001 Timeout: 0 seconds Boot0001: Mageia 2. run grub2-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Mageia --recheck --debug (as per https://wiki.mageia.org/en/UEFI_booting) (no errors reported, everything checks out) 3. run efibootmgr again: BootCurrent: 0001 Timeout: 0 seconds Reproducible: Steps to Reproduce:
Yep, its known. this issue will be resolved when we switch to 3.10 branch when 3.10.22 gets validated
CC: (none) => tmbDepends on: (none) => 11463Assignee: bugsquad => tmb
kernel-3.4.24-2 pushed. http://advisories.mageia.org/MGASA-2013-0371.html
Status: NEW => RESOLVEDResolution: (none) => FIXED