[PLDWWW] page changed: efi

[Jacek Konieczny (jajcus)]

--- https://www.pld-linux.org/efi?rev=1359909100
+++ https://www.pld-linux.org/efi
@@ -7,9 +7,9 @@
  ===== Booting via EFI =====
  
  Requirements:
  
-   * (U)EFI platform (e.g. an IBM xSeries server with recent firmware)
+   * (U)EFI platform (e.g. an IBM xSeries server with recent firmware or a relatively modern laptop, like Lenovo B590)
    * A disk with [[GUID Partition Table]]
    * EFI bootloader (e.g. GRUB2 built for EFI platform, ELILO or Xen or Linux kernel built as an EFI image)
    * EFI-compatible kernel
  
@@ -26,8 +26,12 @@
  
  Not every boot loader is capable of booting from EFI firmware and it is not even necessary to use a dedicated boot loader to start Linux kernel.
  
  The boot loaders with EFI support are: **ELILO** and **GRUB2**.
+ 
+ === No bootloader ===
+ 
+ Recent Linux kernel can boot directly from EFI with no extra boot loader. Also Xen hypervisor can be booted this way (in fact Xen may misbehave if booted under EFI other way). See below.
  
  === ELILO ===
  
  ELILO needs the linux kernel and initrd images present on the EFI System Partition. Specific paths and other options can be
@@ -49,12 +53,8 @@
  
  If the ''Couldn't open either sysfs or procfs directories for accessing EFI variables.'' message is displayed, that means **efibootmgr** was not able to update boot manager configuration. It such case it may be necessary to use the EFI firmware configuration interface (equivalent of 'BIOS setup') to set up booting for ''\grubx64.efi'' or to copy ''/boot/efi/EFI/grub/grubx64.efi'' to ''/boot/efi/EFI/BOOT/BOOTX64.EFI'' file, to make it the default boot loader for the device.
  
  GRUB can also be used for network booting, but version 2.00-1 times out on large initramfs images (this makes PLD Rescue boot impossible).
- 
- === No bootloader ===
- 
- Recent Linux kernel can boot directly from EFI with no extra boot loader. Also Xen hypervisor can be booted this way (in fact Xen may misbehave if booted under EFI other way). See below.
  
  === The default bootloader location ===
  
  Normally the EFI firmware holds a list of configured boot loaders, can present them as a list of boot options or try them automatically in a pre-defined order. This can be managed from Linux using the [[#efibootmgr]] utility. 
@@ -69,8 +69,17 @@
  
  Linux Kernel >= 3.3 can be build in a form, that is also an EFI bootloader (CONFIG_EFI_STUB=y). Such kernel does not need any external boot loader.
  
  PLD Linux kernels have all those features enabled.
+ 
+ == Configuring standard PLD kernel boot ==
+ 
+ To set up kernel boot via EFI with no other boot loader:
+ 
+   * install your kernel and make sure you have a valid ''/boot/initrd'' for it
+   * install [[#efi-boot-update]]
+   * updated /etc/efi-boot/update.d/kernel.conf so it contains proper 'root=' directive in $ARGS (required for Dracut-generated initrd)
+   * run [[#efi-boot-update]] (note, this will only work if already running via EFI)
  
  === Xen ===
  
  [[Xen]] hypervisor acts as a kernel on its own and will load Linux kernel for the dom0 virtual machine. Xen 4.2.0 includes support for EFI boot. In PLD, the xen-efi package provides Xen hypervisor binary for EFI platforms – it acts as an EFI boot loader, so can be booted directly from the firmware or via chain-loading from other EFI boot loader. See the [[Xen]] page for more information.
@@ -90,8 +99,6 @@
  ===== efi-shell =====
  
  Instead of loading a boot loader and starting the operating system one may wish to enter the EFI shell. The EFI shell is often not 
  included in the system firmware and must be installed separately. For convenience, PLD Linux provides the **efi-shell-{ia32,x64}** packages with pre-compiled EFI shell executables. These can be installed like a regular boot-loader – manually or with [[#efi-boot-update]]
- 
- 
  
  


Diff URL:
  https://www.pld-linux.org/efi?do=diff&r1=1359909100&r2=1382684304
-- 
This mail was generated by DokuWiki at
https://www.pld-linux.org/