On 08/27/2015 07:31 PM, Gordon Messmer wrote:
You could:
# efibootmbr -o 0002,0004,0003,0000,0001
wow, not exactly sure what happened...
I ran that script, using 0009,000C,0004,0003 . when I did the efibootmgr
-v, it still showed the existing sequence, 0004,0003.....
then I rebooted. I was all ready to hit F12, when... there were new
entries, and it defaulted to fedora, with my newest kernel, 4.1.6-200 ..
I am assuming the new entries are the rest of the fedora kernels installed..
efibootmgr -v
BootCurrent: 0009
Timeout: 0 seconds
BootOrder: 0005,0009,000C,0004,0003,0010,0000,0001,0002,0008
Boot0000* P0: WDC WD10EZEX-75M2NA0 BBS(17,,0x0)
Boot0001* P4: TSSTcorp DVD+/-RW SH-216DB BBS(19,,0x0)
Boot0002* Fedora
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\fedora\shim.efi)
Boot0003* Windows Boot Manager
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...9................
Boot0004* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0005* Fedora
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\FEDORA\shim.efi)
Boot0008* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Ubuntu\grubx64.efi)
Boot0009* UEFI OS
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000C* UEFI OS
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0010* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Ubuntu\grubx64.efi)
so when I ran the efibootmgr & changed it to default to fedora, it also
used the fedora grub.cfg... is that right?
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587