[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706632: efibootmgr present in Debian Wheezy RC2 is not able to create new entries to boot



On Thu, May 02, 2013 at 02:56:31PM -0300, zen wrote:
>Package: efibootmgr
>Version: 0.5.4-3
>Severity: normal
>
>Dear Maintainer,
>
>efibootmgr present in Debian Wheezy RC2 is not able to create new entries to
>boot on Asus Sabertooth 990FX BIOS 1604
>
>This message is an automatic translation.
>
>After installing Debian Wheezy RC2 discovered that the entry / bootnum UEFI
>boot was not recorded.
>
>After boot the recovery disk, I was not able to record or create a new entry /
>bootnum but dmesg prints this message:
>
>[ 1638.143206] efivars: set_variable() failed: status=8000000000000009
>
>Command used for recording / creation:
># efibootmgr -c -d /dev/sdc -p 1 -l "EFI\debian\grubx64.efi" -L "Test" -v
>
>Successfully made ​​the write / create the entry in the installation disc
>Fedora 18.
>
>/dev/sdc is the disk drive that has the first partition as EF00.

Hi,

I've just taken over maintenance of efibootmgr, and I'm looking at the
bug reports now.

This seems to be an increasingly common issue with new UEFI machines -
it seems that a number of UEFI implementations are bad at managing
space for EFI variables and run out of space. If you reboot, the
chances are that they will clean up a little and allow a new entry to
be written. If you could check that, that may help.

A similar bug has been reported against grub2 with the same symptoms
(bug #706561), and I've added a patch for grub-efi there to reduce the
likelihood of the problem.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Welcome my son, welcome to the machine.


Reply to: