Difference between revisions of "Boot loaders"

From ArchWiki
Jump to: navigation, search
Line 1: Line 1:
 
[[Category:Boot loaders]]
 
[[Category:Boot loaders]]
The boot loader is the first piece of software started by the [[BIOS]] or [[UEFI]]. It is responsible for loading the kernel with the wanted [[kernel parameters]], and [[mkinitcpio|initial RAM disk]] before initiating the [[Arch Boot Process|boot process]]. You can use [[:Category:Boot loaders|different kinds]] of bootloaders in Arch, such as [[GRUB]], [[Syslinux]], [[LILO]] or [[GRUB Legacy]].
+
The boot loader is the first piece of software started by the [[BIOS]] or [[UEFI]]. It is responsible for loading the kernel with the wanted [[kernel parameters]], and [[mkinitcpio|initial RAM disk]] before initiating the [[Arch Boot Process|boot process]]. You can use [[:Category:Boot loaders|different kinds]] of bootloaders in Arch, such as [[GRUB]] and [[Syslinux]]. Some bootloaders only support BIOS or UEFI and some support both.
  
 
This page will only contain a short introduction and the most used configurations that users will encounter. For detailed information, please see the corresponding pages of each boot loader.
 
This page will only contain a short introduction and the most used configurations that users will encounter. For detailed information, please see the corresponding pages of each boot loader.
Line 13: Line 13:
 
=== Syslinux ===
 
=== Syslinux ===
 
See [[Syslinux]].
 
See [[Syslinux]].
 +
 +
== BIOS-only boot loaders ==
 +
 +
=== GRUB Legacy ===
 +
See [[GRUB Legacy]]
  
 
== UEFI-only boot loaders ==
 
== UEFI-only boot loaders ==
  
 
=== Linux Kernel EFISTUB ===
 
=== Linux Kernel EFISTUB ===
 
 
See [[EFISTUB]].
 
See [[EFISTUB]].
  

Revision as of 11:26, 24 October 2013

The boot loader is the first piece of software started by the BIOS or UEFI. It is responsible for loading the kernel with the wanted kernel parameters, and initial RAM disk before initiating the boot process. You can use different kinds of bootloaders in Arch, such as GRUB and Syslinux. Some bootloaders only support BIOS or UEFI and some support both.

This page will only contain a short introduction and the most used configurations that users will encounter. For detailed information, please see the corresponding pages of each boot loader.

Both BIOS and UEFI boot loaders

GRUB

See GRUB.

Note about UEFI support: GRUB 2.x contains its own filesystem drivers and does not rely on the firmware to access the files. It can directly read files from /boot and does not require the kernel and initramfs files to be in the UEFISYS partition. Detailed information at GRUB#UEFI_systems_2. For bzr development version try AUR package - grub-bzrAUR.

Syslinux

See Syslinux.

BIOS-only boot loaders

GRUB Legacy

See GRUB Legacy

UEFI-only boot loaders

Linux Kernel EFISTUB

See EFISTUB.

Troubleshooting

Bootloader does not show up in UEFI menu

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: This troubleshooting note has been transferred from Beginners' Guide as discussed on the talk page. It is not yet well integrated here and is rather selective in terms of the help provided. (Discuss in Talk:Boot loaders#)

On some UEFI motherboards like the Intel Z77 boards, adding entries with efibootmgr or bcfg from efi shell will not work because they don't show up on the boot menu list after being added to NVRAM.

To solve this you have to trick the UEFI firmware that Windows boot manager is present on the ESP partition.

Copy the bootx64.efi file from USB drive as bootmgfw.efi efi file to your ESP partition by booting into EFI shell and typing:

FS1:
cd EFI
mkdir Microsoft
cd Microsoft
mkdir Boot
cp FS0:\EFI\BOOT\bootx64.efi FS1:\EFI\Microsoft\Boot\bootmgfw.efi

After reboot, any entries added to NVRAM should show up in the boot menu.

See also