Boot loaders

From ArchWiki
Revision as of 16:24, 22 March 2014 by Teateawhy (talk | contribs) (Updated wording and removed too detailed information.)
Jump to: navigation, search

zh-CN: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 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 contains a short introduction about bootloaders available in Arch. For detailed information see the corresponding pages of each bootloader.

Both BIOS and UEFI boot loaders




See Syslinux.


Note: BURG is not officially supported by Arch developers.


UEFI-only boot loaders

Linux Kernel EFISTUB

The Linux kernel can be booted directly without a boot loader. The stock Archlinux kernel has the EFI stub loader built in. See EFISTUB.


Gummiboot is a UEFI Boot Manager which provides a menu for booting EFISTUB kernels. See Gummiboot.


rEFInd is a UEFI Boot Manager which provides a menu for booting EFISTUB kernels. It is an alternative to Gummiboot. See rEFInd.


Warning: ELILO upstream has clarified that it is no longer in active development, meaning no new features will be added and only bug-fixes are released. See for more information. ELILO is not officially supported by Arch developers.

ELILO is the UEFI version of the BIOS-only LILO. Its config file elilo.conf is similar to LILO's config file. Upstream provided compiled binaries are available at and an AUR package at elilo-efiAUR.

BIOS-only boot loaders

GRUB Legacy

Note: GRUB Legacy is not officially supported by Arch developers.

GRUB Legacy (also known as grub-0.97), is the legacy, BIOS-only branch of GRUB. See GRUB Legacy.


Note: LILO is not officially supported by Arch developers but it does continue to be actively developed.



Note: NeoGRUB is not officially supported by Arch developers.

NeoGRUB provides a means to boot Arch from the Windows boot loader without installing an additional boot loader. See NeoGRUB.

Booting Arch from NeoGRUB has not been tested yet from Windows 8 and/or UEFI systems.


UEFI boot loader does not show up in firmware menu

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

This issue is caused because the motherboards can only load Microsoft Windows. To solve this you have to place the .efi file in the location that Windows uses.

Copy the bootx64.efi file from the Arch Linux installation medium (FSO:) to the Microsoft directory your ESP partition on your hard drive (FS1:). Do this by booting into EFI shell and typing:

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