Sample Header Ad - 728x90

EFI Boot list and EFI Boot Manager timeout setting not working

1 vote
1 answer
2946 views
How can I change the 'timeout' setting of the EFI boot manager? I am trying to dual-boot Windows 8 and Ubuntu and I would like to be able to choose one or the other OS at my machine boot time. I already tried to use sudo efibootmgr -t 10 from within Ubuntu, but that didn't work for me as I don't see a list to choose from when my computer loads but boots directly to grub. Here are more details:
$ efibootmgr -v
BootCurrent: 0000
Timeout: 10 seconds
BootOrder: 0000,0002
Boot0000* debian        HD(13,GPT,007a058a-8e5e-45df-8d97-6575b66b5355,0x1afa9000,0x113000)/File(\EFI\debian\grubx64.efi)
Boot0002* Windows Boot Manager  HD(13,GPT,007a058a-8e5e-45df-8d97-6575b66b5355,0x1afa9000,0x113000)/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.}....................

$ bootctl status
systemd-boot not installed in ESP.
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /efi (/dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355)
         File: `-/EFI/BOOT/bootx64.efi

Boot Loaders Listed in EFI Variables:
        Title: debian
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355
         File: `-/EFI/debian/grubx64.efi

        Title: Windows Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355
         File: `-/EFI/Microsoft/Boot/bootmgfw.efi

Boot Loader Entries:
        $BOOT: /efi (/dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355)

0 entries, no entry could be determined as default.
Is it because of the systemd-boot not installed in ESP? **UPDATE:** Here is my status after carrying out the tasks in Peter's answer.
$ efibootmgr -v
BootCurrent: 0000
Timeout: 6 seconds
BootOrder: 0001,0000,0002
Boot0000* debian        HD(13,GPT,007a058a-8e5e-45df-8d97-6575b66b5355,0x1afa9000,0x113000)/File(\EFI\debian\grubx64.efi)
Boot0001* Linux Boot Manager    HD(13,GPT,007a058a-8e5e-45df-8d97-6575b66b5355,0x1afa9000,0x113000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0002* Windows Boot Manager  HD(13,GPT,007a058a-8e5e-45df-8d97-6575b66b5355,0x1afa9000,0x113000)/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.}....................

$ bootctl status
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /efi (/dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355)
         File: `-/EFI/systemd/systemd-bootx64.efi (systemd-boot 245.4-4ubuntu3.1)
         File: `-/EFI/BOOT/bootx64.efi (systemd-boot 245.4-4ubuntu3.1)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355
         File: `-/EFI/systemd/systemd-bootx64.efi

        Title: debian
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355
         File: `-/EFI/debian/grubx64.efi

        Title: Windows Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355
         File: `-/EFI/Microsoft/Boot/bootmgfw.efi

Boot Loader Entries:
        $BOOT: /efi (/dev/disk/by-partuuid/007a058a-8e5e-45df-8d97-6575b66b5355)

0 entries, no entry could be determined as default.

$ cat "$(bootctl -x)/loader/loader.conf"
#timeout 3
#console-mode keep
default f1439fc415644fedb2360e6691283080-*

timeout 5
console-mode max
editor yes
auto-entries yes
auto-firmware yes
random-seed-mode always

$ bootctl status | grep f1439fc415644fe | wc
      0       0       0
So Peter, - where does the default f1439fc415644fedb2360e6691283080-* comes from in the /loader/loader.conf file and what does it means? And what did you mean when you put default Windows there? - and most importantly, I now can see that EFI Boot list/menu, just it has Windows Boot Manager and the Reboot into firmware your mentioned, but it doesn't have the Linux / debian menu that I want. what I'm missing?
Asked by xpt (1858 rep)
Sep 6, 2021, 04:32 AM
Last activity: Apr 18, 2025, 10:02 PM