Difference between revisions of "Category:Boot loaders"

From ArchWiki
Jump to: navigation, search
m (grub2 is now grub, grub1 is grub-legacy)
m (Feature comparison: typo)
 
(45 intermediate revisions by 8 users not shown)
Line 1: Line 1:
<noinclude>[[Category:Boot process]]
+
[[Category:Boot process]]
 +
[[ar:Category:Boot loaders]]
 +
[[el:Category:Boot loaders]]
 
[[es:Category:Boot loaders]]
 
[[es:Category:Boot loaders]]
 
[[id:Category:Boot loaders]]
 
[[id:Category:Boot loaders]]
 
[[it:Category:Boot loaders]]
 
[[it:Category:Boot loaders]]
[[zh-CN:Category:Boot loaders]]
+
[[ja:Category:ブートローダー]]
</noinclude>In order to boot Arch Linux, a Linux-capable boot loader such as [[GRUB]](2), [[Syslinux]], [[LILO]] or [[GRUB Legacy]] must be installed to the [[Master Boot Record]] or the [[GUID Partition Table]]. The boot loader is responsible for loading the kernel and [[mkinitcpio|initial ramdisk]] before initiating the [[Arch Boot Process|boot process]].
+
[[pt:Category:Boot loaders]]
 +
[[ru:Category:Boot loaders]]
 +
[[zh-cn:Category:Boot loaders]]
 +
[[zh-tw:Category:Boot loaders]]
 +
In order to boot Arch Linux, a Linux-capable boot loader must be installed to the [[Master Boot Record]] or the [[GUID Partition Table]]. It 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 [[boot process]].
 +
 
 +
{{Note|Loading [[Microcode]] updates requires adjustments in boot loader configuration. [https://www.archlinux.org/news/changes-to-intel-microcodeupdates/]}}
 +
 
 +
== Feature comparison ==
 +
 
 +
{{Note|
 +
* Boot loaders only need to support the file system on which kernel and initramfs reside (the file system of the partition on which {{ic|/boot}} is located).
 +
* As GPT is part of the UEFI specification, all UEFI boot loaders support GPT disks. GPT on BIOS systems is possible, using either "hybrid booting", or the new [http://repo.or.cz/syslinux.git/blob/HEAD:/doc/gpt.txt GPT-only] protocol. This protocol may however cause issues with certain BIOS implementations; see [http://www.rodsbooks.com/gdisk/bios.html#bios rodsbooks] for details.
 +
* Encryption mentioned in file system support is [[wikipedia:Filesystem-level encryption|filesystem-level encryption]], it has no bearing on [[dm-crypt|block-level encryption]].
 +
}}
 +
 
 +
{{Expansion|Fill in the unknowns.}}
 +
 
 +
{| class="wikitable"
 +
! rowspan="2"| Name
 +
! colspan="2"| Firmware
 +
! rowspan="2"| Multi-boot
 +
! colspan="5"| [[File systems]]
 +
! rowspan="2"| Notes
 +
|-
 +
! BIOS !! [[UEFI]]
 +
! [[Btrfs]] !! [[ext4]] !! ReiserFS v3 !! [[VFAT]] !! [[XFS]]
 +
|-
 +
| [[GRUB]]
 +
| {{Yes}} || {{Yes}}
 +
| {{Yes}}
 +
| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
 +
| On BIOS/GPT configuration requires [[GRUB#GUID Partition Table (GPT) specific instructions|GRUB BIOS boot partition]].
 +
|-
 +
| [[systemd-boot]]
 +
| {{No}} || {{Yes}}
 +
| {{Yes}}
 +
| {{No}} || {{No}} || {{No}} || {{Yes}} || {{No}}
 +
| Cannot launch binaries from partitions other than [[ESP]].
 +
|-
 +
| [[Syslinux]]
 +
| {{Yes}} || {{Y|[[Syslinux#Limitations_of_UEFI_Syslinux|Partial]]}}
 +
| {{Y|[[Syslinux#Chainloading|Partial]]}}
 +
| {{Y|without: multi-device volumes, compression, encryption}} || {{Y|without: {{ic|64bit}} feature, encryption}} || {{No}} || {{Yes}} || {{Y|v4 on [[MBR]] only}}
 +
| No support for certain [[file system]] features [http://www.syslinux.org/wiki/index.php?title=Filesystem]
 +
|-
 +
| [[EFISTUB]]
 +
| {{No}} || {{Yes}}
 +
| {{Grey|N/A}}
 +
| {{Grey|N/A}} || {{Grey|N/A}} || {{Grey|N/A}} || {{Grey|N/A}} || {{Grey|N/A}}
 +
|
 +
|-
 +
| [[rEFInd]]
 +
| {{No}} || {{Yes}}
 +
| {{Yes}}
 +
| {{Y|without encryption}} || {{Y|without encryption}} || {{Y|without tail-packing feature}} || {{Yes}} || {{No}}
 +
|
 +
|-
 +
| [[Clover]]
 +
| {{G|emulates UEFI}} || {{Yes}}
 +
| {{Yes}}
 +
| {{No}} || Unknown || {{No}} || {{Yes}} || {{No}}
 +
| Main target audience is [[wikipedia:Hackintosh|Hackintosh]] users.
 +
|-
 +
| [[LILO]]
 +
| {{Yes}} || {{No}}
 +
| Unknown
 +
| Unknown || Unknown || Unknown || Unknown || {{Y|MBR only [http://xfs.org/index.php/XFS_FAQ#Q:_Does_LILO_work_with_XFS.3F]}}
 +
| [https://lists.alioth.debian.org/pipermail/lilo-devel/2015-December/000083.html Deprecated]. Does not support [[GUID Partition Table]].
 +
|-
 +
| [[GRUB Legacy]]
 +
| {{Yes}} || {{No}}
 +
| {{Yes}}
 +
| {{No}} || {{No}} || {{Yes}} || {{Yes}} || {{Y|v4 only}}
 +
| [https://www.gnu.org/software/grub/grub-legacy.html Deprecated]. Does not support [[GUID Partition Table]].
 +
|-
 +
| [[NeoGRUB]]
 +
| {{Yes}} || {{No}}
 +
| {{Yes}}
 +
| Unknown || Unknown || Unknown || Unknown || Unknown
 +
|
 +
|}
 +
 
 +
== 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://www.kernel.org/doc/Documentation/efi-stub.txt 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 11:51, 30 October 2016

In order to boot Arch Linux, a Linux-capable boot loader must be installed to the Master Boot Record or the GUID Partition Table. It 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.

Note: Loading Microcode updates requires adjustments in boot loader configuration. [1]

Feature comparison

Note:
  • Boot loaders only need to support the file system on which kernel and initramfs reside (the file system of the partition on which /boot is located).
  • As GPT is part of the UEFI specification, all UEFI boot loaders support GPT disks. GPT on BIOS systems is possible, using either "hybrid booting", or the new GPT-only protocol. This protocol may however cause issues with certain BIOS implementations; see rodsbooks for details.
  • Encryption mentioned in file system support is filesystem-level encryption, it has no bearing on block-level encryption.

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the unknowns. (Discuss in Category talk:Boot loaders#)
Name Firmware Multi-boot File systems Notes
BIOS UEFI Btrfs ext4 ReiserFS v3 VFAT XFS
GRUB Yes Yes Yes Yes Yes Yes Yes Yes On BIOS/GPT configuration requires GRUB BIOS boot partition.
systemd-boot No Yes Yes No No No Yes No Cannot launch binaries from partitions other than ESP.
Syslinux Yes Partial Partial without: multi-device volumes, compression, encryption without: 64bit feature, encryption No Yes v4 on MBR only No support for certain file system features [2]
EFISTUB No Yes N/A N/A N/A N/A N/A N/A
rEFInd No Yes Yes without encryption without encryption without tail-packing feature Yes No
Clover emulates UEFI Yes Yes No Unknown No Yes No Main target audience is Hackintosh users.
LILO Yes No Unknown Unknown Unknown Unknown Unknown MBR only [3] Deprecated. Does not support GUID Partition Table.
GRUB Legacy Yes No Yes No No Yes Yes v4 only Deprecated. Does not support GUID Partition Table.
NeoGRUB Yes No Yes Unknown Unknown Unknown Unknown Unknown

See also

Pages in category "Boot loaders"

The following 11 pages are in this category, out of 11 total.