efibootmgr(8)

1EFIBOOTMGR(8)                                                    EFIBOOTMGR(8)
2
3
4

NAME

6       efibootmgr - manipulate the EFI Boot Manager
7

SYNOPSIS

9       efibootmgr  [  -a ] [ -A ] [ -b XXXX ] [ -B XXXX ] [ -c ] [ -d DISK ] [
10       -e 1|3|-1 ] [ -E NUM ] [ -g ] [ -H XXXX ] [ -i NAME ] [ -l NAME ] [  -L
11       LABEL ] [ -n XXXX ] [ -N ] [ -o XXXX,YYYY,ZZZZ ... ] [ -O ] [ -p PART ]
12       [ -q ] [ -t seconds ] [ -T ] [ -u ] [ -U XXXX ] [ -v ] [ -V ] [ -w ]  [
13       -@ file ]
14
15

DESCRIPTION

17       efibootmgr is a userspace application used to modify the Intel Extensi‐
18       ble Firmware Interface (EFI) Boot Manager.  This application can create
19       and  destroy  boot entries, change the boot order, change the next run‐
20       ning boot option, and more.
21
22       Details on the EFI Boot Manager are available from the  EFI  Specifica‐
23       tion, v1.02 or later, available from:
24        <URL:http://developer.intel.com>
25
26              Note:  efibootmgr requires that the kernel support access to EFI
27              non-volatile variables (through /proc/efi/vars on  2.4  kernels,
28              /sys/firmware/efi/vars on 2.6 kernels).  modprobe efivars should
29              do the trick.
30

OPTIONS

32       The following is a list of options accepted by efibootmgr:
33
34       -a | --active
35              Sets bootnum active
36
37       -A | --inactive
38              Sets bootnum inactive
39
40       -b | --bootnum XXXX
41              Modify BootXXXX (hex)
42
43       -B | --delete-bootnum
44              Delete bootnum (hex)
45
46       -c | --create
47              Create new variable bootnum and add to bootorder
48
49       -d | --disk DISK
50              The disk containing the loader (defaults to /dev/sda)
51
52       -e | --edd 1|3|-1
53              Force EDD 1.0 or 3.0 creation variables, or guess.
54
55       -E | --device NUM
56              EDD 1.0 device number (defaults to 0x80)
57
58       -g | --gpt
59              Force disk with invalid PMBR to be treated as GPT
60
61       -H | --acpi_hid XXXX
62              set the ACPI HID (used with -i)
63
64       -i | --iface NAME
65              create a netboot entry for the named interface
66
67       -l | --loader NAME
68              Specify a loader (defaults to \\elilo.efi)
69
70       -L | --label LABEL
71              Boot manager display label (defaults to "Linux")
72
73       -n | --bootnext XXXX
74              Set BootNext to XXXX (hex)
75
76       -N | --delete-bootnext
77              Delete BootNext
78
79       -o | --bootorder XXXX,YYYY,ZZZZ
80              Explicitly set BootOrder (hex)
81
82       -O | --delete-bootorder
83              Delete BootOrder
84
85       -p | --part PART
86              Partition number containing the bootloader (defaults to 1)
87
88       -q | --quiet
89              Quiet mode - supresses output.
90
91       --test filename
92              Don't write to NVRAM, write to filename.
93
94       -t | --timeout seconds
95              Boot Manager timeout, in seconds.
96
97       -T | --delete-timeout
98              Delete Timeout variable.
99
100       -u | --unicode | --UCS-2
101              pass extra command line arguments as UCS-2 (default is ASCII)
102
103       -U | --acpi_uid XXXX
104              set the ACPI UID (used with -i)
105
106       -v | --verbose
107              Verbose mode - prints additional information
108
109       -V | --version
110              Just print version string and exit.
111
112       -w | --write-signature
113              write unique signature to the MBR if needed
114
115       -@ | --append-binary-args
116              append extra variable args from file (use - to read from stdin).
117              Data  in  file is appended as command line arguments to the boot
118              loader command, with no modification to the  data,  so  you  can
119              pass any binary or text data necessary.
120

EXAMPLES

122       1.
123
124   DISPLAYING THE CURRENT SETTINGS (MUST BE ROOT).
125       [root@localhost   ~]#   efibootmgr  BootCurrent:  0004  BootNext:  0003
126       BootOrder:  0004,0000,0001,0002,0003  Timeout:  30  seconds   Boot0000*
127       Diskette  Drive(device:0)  Boot0001*  CD-ROM Drive(device:FF) Boot0002*
128       Hard   Drive(Device:80)/HD(Part1,Sig00112233)   Boot0003*   PXE   Boot:
129       MAC(00D0B7C15D91) Boot0004* Linux
130
131       This shows:
132
133              · BootCurrent  - the boot entry used to start the currently run‐
134                ning system
135
136              · BootOrder - the boot order as would appear in  the  boot  man‐
137                ager.   The  boot manager tries to boot the first active entry
138                in this list.  If unsuccessful, it tries the next  entry,  and
139                so on.
140
141              · BootNext - the boot entry which is scheduled to be run on next
142                boot.  This supercedes BootOrder for one  boot  only,  and  is
143                deleted  by the boot manager after first use.  This allows you
144                to change the next boot behavior without changing BootOrder.
145
146              · Timeout - the time in seconds between when  the  boot  manager
147                appears  on the screen until when it automatically chooses the
148                startup value from BootNext or BootOrder.
149
150              · Five boot entries (0000 - 0004), along with  the  active/inac‐
151                tive  flag  (*  means  active)  and  the name displayed on the
152                screen.
153
154       2.
155
156   CREATING A NEW BOOT OPTION
157       An OS installer would call efibootmgr -c.  This assumes that  /boot/efi
158       is  your  EFI System Partition, and is mounted at /dev/sda1.  This cre‐
159       ates a new boot option, called "Linux", and puts it at the top  of  the
160       boot order list.  Options may be passed to modify the default behavior.
161       The default OS Loader is elilo.efi.
162
163       3.
164
165   CHANGING THE BOOT ORDER
166       Assuming the configuration in Example #1, efibootmgr -o  3,4  could  be
167       called to specify PXE boot first, then Linux boot.
168
169       4.
170
171   CHANGING THE BOOT ORDER FOR THE NEXT BOOT ONLY
172       Assuming  the  configuration  in  Example  #1, efibootmgr -n 4 could be
173       called to specify that the Linux entry be taken on next boot.
174
175       5.
176
177   DELETING A BOOT OPTION
178       Assuming the configuration in Example #1, efibootmgr -b 4 -B  could  be
179       called to delete entry 4 and remove it from the BootOrder.
180
181       6.
182
183   CREATING NETWORK BOOT ENTRIES
184       A  system  administrator  wants to create a boot option to network boot
185       (PXE).  Unfortunately, this requires knowing a little more  information
186       about your system than can be easily found by efibootmgr, so you've got
187       to pass additional information - the ACPI HID and  UID  values.   These
188       can  generally be found by using the EFI Boot Manager (in the EFI envi‐
189       ronment) to create a network boot entry, then using efibootmgr to print
190       it       verbosely.        Here's       one      example:      Boot003*
191       Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510)                            \
192       ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0)  In  this case, the ACPI HID
193       is "0A0341d0" and the UID is "0".  For the  zx2000  gigE,  the  HID  is
194       "222F"  and  the  UID is "500".  For the rx2000 gigE, the HID is "0002"
195       and the UID is "100".  You create the boot entry with: efibootmgr -c -i
196       eth0 -H 222F -U 500 -L netboot
197

BUGS

199       Please  direct  any  bugs,  features,  patches,  etc.  to  Matt  Domsch
200       <Matt_Domsch@dell.com>.
201

AUTHOR

203       This man page was generated by dann frazier <dannf@debian.org> for  the
204       Debian GNU/Linux operating system, but may be used by others.
205