Now Bug 1047993 - Re: [Bug 1006304] BootLoaderError: failed to set new efi boot target

Robert Moskowitz rgm at htt-consult.com
Thu Jan 2 20:24:39 UTC 2014


I did the testing as you suggested and opened up a kernel bug report.

On 01/01/2014 04:26 PM, Chris Murphy wrote:
> On Jan 1, 2014, at 1:07 PM, Chris Murphy <lists at colorremedies.com> wrote:
>
>>>> efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
>>>>
>>>> And see if you get an error; and you can also reissue efibootmgr -v to see if that entry is now in NVRAM to confirm.
>>> No errors and no change to NVRAM.
>> Any new messages in dmesg at the time you issued the efibootmgr command?
> If not try this:
>
> dmesg -n7          #increases kernel log level
> dmesg         #get a baseline dmesg, note last entry
> efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
> dmesg        #check to see if there's a new entry
> efibootmgr -v     #check if there's a Fedora entry added
>


More information about the test mailing list