Difference between revisions of "Boot loaders"

From ArchWiki
Jump to: navigation, search
m (NeoGRUB)
 
(46 intermediate revisions by 22 users not shown)
Line 1: Line 1:
[[Category:Boot loaders]]
+
#REDIRECT: [[:Category:Boot loaders]]
[[ja:Boot Loaders]]
+
The boot loader is the first piece of software started by the [[Wikipedia:BIOS|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.
+
 
+
== 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 {{ic|/boot}} and does not require the kernel and initramfs files to be in the UEFISYS partition. Detailed information at [[GRUB#UEFI_systems_2]]. For GIT development version try AUR package - {{AUR|grub-git}}}}
+
 
+
=== Syslinux ===
+
 
+
See [[Syslinux]]
+
 
+
== UEFI-only Boot Loaders ==
+
 
+
=== Linux Kernel EFISTUB ===
+
 
+
Follow [[EFISTUB]]
+
 
+
==== Gummiboot ====
+
 
+
Gummiboot is a UEFI Boot Manager (not a boot loader) which provides a menu for EFISTUB kernels. For more info follow [[Gummiboot]].
+
 
+
==== rEFInd ====
+
 
+
rEFInd is a UEFI Boot Manager which provides a menu for EFISTUB kernels. It is alternative to Gummiboot. For more info follow [[EFISTUB#Using_rEFInd|rEFInd]].
+
 
+
=== ELILO ===
+
 
+
ELILO is the UEFI version of LILO Boot Loader (although it does not share code with BIOS based [[LILO]] boot loader). It was originally created for Intel Itanium systems which supported only EFI 1.x (precursor to UEFI 2.x). It is the oldest UEFI bootloader for Linux. Elilo config file {{ic|elilo.conf}} is similar to [[LILO]]'s config file. ELILO does not support chainloading other EFI applications. and does not provide a menu by default (setting up requires additional configuration as described in {{ic|elilo/docs/textmenu_chooser.txt}} file. Upstream provided compiled binaries are available at http://sourceforge.net/projects/elilo/ and AUR package at {{AUR|elilo-efi}}.
+
 
+
{{Warning|1=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 https://sourceforge.net/mailarchive/message.php?msg_id=31524008 for more info. '''ELILO is not officially supported by Arch devs.'''}}
+
 
+
== BIOS-only Boot Loaders ==
+
 
+
=== GRUB Legacy ===
+
 
+
Follow [[GRUB Legacy]]
+
 
+
{{Note|GRUB Legacy (also known as grub-0.97) is not officially supported by Arch devs.}}
+
 
+
=== LILO ===
+
 
+
Follow [[LILO]]
+
 
+
{{Note|LILO is not officially supported by Arch devs, although it seems to be actively developed.}}
+
 
+
=== NeoGRUB ===
+
 
+
[[NeoGRUB]] provides a means to boot Arch from the Windows Bootloader without installing a bootloader on the Arch itself. It is provided by the EasyBCD tool running on Windows. This is a great option for dual-booting Windows and Arch, especially if you find that Windows has trouble when booted or chainloaded from Syslinux or GRUB.
+
 
+
{{Note|NeoGRUB is not officially supported by Arch devs.}}
+
 
+
== Troubleshooting ==
+
 
+
=== UEFI Boot Loader does not show up in firmware menu ===
+
 
+
On some UEFI motherboards like boards with an Intel Z77 chipset, adding entries with {{ic|efibootmgr}} or {{ic|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 {{ic|.efi}} file in the location that Windows uses.
+
 
+
Copy the {{ic|bootx64.efi}} file from the Arch Linux installation medium ({{ic|FSO:}}) to the Microsoft directory your ESP partition on your hard drive ({{ic|FS1:}}). Do this 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 ==
+
 
+
* [http://www.rodsbooks.com/efi-bootloaders/ Rod Smith - Managing EFI Boot Loaders for Linux]
+
* [http://www.rodsbooks.com/refind/ Rod Smith - rEFInd, a fork or rEFIt]
+
* [https://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=Documentation/x86/efi-stub.txt;hb=HEAD Linux Kernel Documentation on EFISTUB]
+
* [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=291f36325f9f252bd76ef5f603995f37e453fc60;hp=55839d515495e766605d7aaabd9c2758370a8d27 Linux Kernel EFISTUB Git Commit]
+
* [http://www.rodsbooks.com/efi-bootloaders/efistub.html Rod Smith's page on EFISTUB]
+
* [http://www.rodsbooks.com/refind/linux.html rEFInd Documentation for booting EFISTUB Kernels]
+

Latest revision as of 10:02, 6 July 2016