After the Software Updater run of 7/9/2015, a new 3.13.0-57 kernel
(signed and unsigned) was added, and something added the "Boot0000,
ubuntu, shim" bootloader entry again, at the first position (where it
originally was).  I did nothing explicit to add this shim entry, and the
machine is running with secure boot disabled.  Attached is the
efibootmgr output and the diff of fwts outputs.  My Ubuntu boot default
was restored, but something seems wrong with the update process changing
nvram.

$ sudo efibootmgr -v                                                            
                                        
BootCurrent: 0000                                                               
                                        
Timeout: 2 seconds                                                              
                                        
BootOrder: 0000,0004,0003,2003,2001,2002                                        
                                        
Boot0000* ubuntu    
HD(2,e1800,82000,04b9edc2-fc48-11e1-8ec1-e7137b3aaf29)File(\EFI\ubuntu\shimx64.efi)
                 
Boot0001* EFI Network 0 for IPv6 (00-8C-FA-3B-27-AA)    
ACPI(a0341d0,0)PCI(1c,0)PCI(0,0)MAC(008cfa3b27aa,0)030d3c000000$
Boot0002* EFI Network 0 for IPv4 (00-8C-FA-3B-27-AA)    
ACPI(a0341d0,0)PCI(1c,0)PCI(0,0)MAC(008cfa3b27aa,0)IPv4(0.0.0.0$
Boot0003* Ubuntu    
HD(2,e1800,82000,04b9edc2-fc48-11e1-8ec1-e7137b3aaf29)File(\EFI\ubuntu\grubx64.efi)RC
               
Boot0004* Windows Boot Manager  
HD(2,e1800,82000,04b9edc2-fc48-11e1-8ec1-e7137b3aaf29)File(\EFI\Microsoft\Boot\bootmgfw$
Boot2001* EFI USB Device    RC                                                  
                                        
Boot2002* EFI DVD/CDROM RC                                                      
                                        
Boot2003* EFI Network   RC 


$ diff results.log fwtwuefidumpnewdefault.log
6c6
< This test run on 09/07/15 at 21:55:03 on host Linux tosi 3.19.8-992-generic
---
> This test run on 09/07/15 at 13:27:54 on host Linux tosi 3.19.8-992-generic
51,57d50
< Name: Boot0000.
<   GUID: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C
<   Attr: 0x7 (NonVolatile,BootServ,RunTime).
<   Active: Yes
<   Info: ubuntu
<   Path: 
\HARDDRIVE(2,e1800,82000,c2edb90448fce111,8e,c1)\FILE('\EFI\ubuntu\shimx64.efi').
< 
110c103
<   BootCurrent: 0x0000.
---
>   BootCurrent: 0x0003.
115c108
<   Boot Order: 0x0000,0x0004,0x0003,0x2003,0x2001,0x2002.
---
>   Boot Order: 0x0004,0x0003,0x2003,0x2001,0x2002.
121c114
<   Data: 0000: 00 00                                            ..
---
>   Data: 0000: 03 00                                            ..
133c126
<   Data: 0060: 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00  
\.s.h.i.m.x.6.4.
---
>   Data: 0060: 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00  
> \.g.r.u.b.x.6.4.
1119,1120c1112,1113
<   Size: 10 bytes of data.
<   Data: 0000: 00 00 04 00 03 00 02 00 01 00                    ..........
---
>   Size: 8 bytes of data.
>   Data: 0000: 04 00 03 00 02 00 01 00                          ........

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286388

Title:
  changes to the boot order made via efibootmgr are not sticking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1286388/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to