Installation guide

This document is a guide for installing Arch Linux using the live system booted from an installation medium made from an official installation image. The installation medium provides accessibility features which are described on the page Install Arch Linux with accessibility options. For alternative means of installation, see Category:Installation process.

Before installing, it would be advised to view the FAQ. For conventions used in this document, see Help:Reading. In particular, code examples may contain placeholders (formatted in italics) that must be replaced manually.

For more detailed instructions, see the respective ArchWiki articles or the various programs' man pages, both linked from this guide. For interactive help, the IRC channel and the forums are also available.

Arch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM, though more memory is needed to boot the live system for installation. A basic installation should take less than 2 GiB of disk space. As the installation process needs to retrieve packages from a remote repository, this guide assumes a working internet connection is available.


Acquire an installation image

Visit the Download page and, depending on how you want to boot, acquire the ISO file or a netboot image, and the respective GnuPG signature.

Verify signature

It is recommended to verify the image signature before use, especially when downloading from an HTTP mirror, where downloads are generally prone to be intercepted to serve malicious images.

On a system with GnuPG installed, do this by downloading the ISO PGP signature (under Checksums in the page Download) to the ISO directory, and verifying it with:

$ gpg --keyserver-options auto-key-retrieve --verify archlinux-version-x86_64.iso.sig

Alternatively, from an existing Arch Linux installation run:

$ pacman-key -v archlinux-version-x86_64.iso.sig
  • The signature itself could be manipulated if it is downloaded from a mirror site, instead of from as above. In this case, ensure that the public key, which is used to decode the signature, is signed by another, trustworthy key. The gpg command will output the fingerprint of the public key.
  • Another method to verify the authenticity of the signature is to ensure that the public key's fingerprint is identical to the key fingerprint of the Arch Linux developer who signed the ISO-file. See Wikipedia:Public-key cryptography for more information on the public-key process to authenticate keys.

Prepare an installation medium

The installation image can be supplied to the target machine via a USB flash drive, an optical disc or a network with PXE: follow the appropriate article to prepare yourself an installation medium from the chosen image.

Boot the live environment

Note: Arch Linux installation images do not support Secure Boot. You will need to disable Secure Boot to boot the installation medium. If desired, Secure Boot can be set up after completing the installation.
  1. Point the current boot device to the one which has the Arch Linux installation medium. Typically it is achieved by pressing a key during the POST phase, as indicated on the splash screen. Refer to your motherboard's manual for details.
  2. When the installation medium's boot loader menu appears, select Arch Linux install medium and press Enter to enter the installation environment.
    Tip: The installation image uses GRUB for UEFI and syslinux for BIOS booting. See README.bootparams for a list of boot parameters.
  3. You will be logged in on the first virtual console as the root user, and presented with a Zsh shell prompt.

To switch to a different console—for example, to view this guide with Lynx alongside the installation—use the Alt+arrow shortcut. To edit configuration files, mcedit(1), nano and vim are available. See pkglist.x86_64.txt for a list of the packages included in the installation medium.

Set the console keyboard layout

The default console keymap is US. Available layouts can be listed with:

# ls /usr/share/kbd/keymaps/**/*.map.gz

To set the keyboard layout, pass a corresponding file name to loadkeys(1), omitting path and file extension. For example, to set a German keyboard layout:

# loadkeys de-latin1

Console fonts are located in /usr/share/kbd/consolefonts/ and can likewise be set with setfont(8).

Verify the boot mode

To verify the boot mode, list the efivars directory:

# ls /sys/firmware/efi/efivars

If the command shows the directory without error, then the system is booted in UEFI mode. If the directory does not exist, the system may be booted in BIOS (or CSM) mode. If the system did not boot in the mode you desired, refer to your motherboard's manual.

Connect to the internet

To set up a network connection in the live environment, go through the following steps:

  • Ensure your network interface is listed and enabled, for example with ip-link(8):
  • For wireless and WWAN, make sure the card is not blocked with rfkill.
  • Connect to the network:
    • Ethernet—plug in the cable.
    • Wi-Fi—authenticate to the wireless network using iwctl.
    • Mobile broadband modem—connect to the mobile network with the mmcli utility.
  • Configure your network connection:
  • The connection may be verified with ping:
    # ping

Update the system clock

In the live environment systemd-timesyncd is enabled by default and time will be synced automatically once a connection to the internet is established.

Use to ensure the system clock is accurate:

# timedatectl status

Partition the disks

When recognized by the live system, disks are assigned to a block device such as /dev/sda, or . To identify these devices, use lsblk or fdisk.

# fdisk -l

Results ending in , or may be ignored.

The following partitions are required for a chosen device:

If you want to create any stacked block devices for LVM, system encryption or RAID, do it now.

Use fdisk or parted to modify partition tables. For example:

# fdisk /dev/the_disk_to_be_partitioned

Example layouts

Mount point Partition Partition type Suggested size
/mnt/boot1 EFI system partition At least 300 MiB
/dev/swap_partition Linux swap More than 512 MiB
Linux x86-64 root (/) Remainder of the device
  1. Other mount points, such as , are possible, provided that the used boot loader is capable of loading the kernel and initramfs images from the root volume. See the warning in Arch boot process#Boot loader.
Mount point Partition Partition type Suggested size
/dev/swap_partition Linux swap More than 512 MiB
Linux Remainder of the device

See also Partitioning#Example layouts.

Format the partitions

Once the partitions have been created, each newly created partition must be formatted with an appropriate file system. See File systems#Create a file system for details.

For example, to create an Ext4 file system on , run:

# mkfs.ext4 /dev/root_partition

If you created a partition for swap, initialize it with :

# mkswap /dev/swap_partition

If you created an EFI system partition, format it to FAT32 using .

# mkfs.fat -F 32 /dev/efi_system_partition

Mount the file systems

Mount the root volume to . For example, if the root volume is :

# mount /dev/root_partition /mnt

Create any remaining mount points (such as ) and mount their corresponding volumes.

Tip: Run mount(8) with the --mkdir option to create the specified mount point. Alternatively, create it using mkdir(1) beforehand.

For UEFI systems, mount the EFI system partition:

# mount --mkdir /dev/efi_system_partition /mnt/boot

If you created a swap volume, enable it with :

# swapon /dev/swap_partition
will later detect mounted file systems and swap space.


Select the mirrors

Packages to be installed must be downloaded from mirror servers, which are defined in . On the live system, after connecting to the internet, reflector updates the mirror list by choosing 20 most recently synchronized HTTPS mirrors and sorting them by download rate.

The higher a mirror is placed in the list, the more priority it is given when downloading a package. You may want to inspect the file to see if it is satisfactory. If it is not, edit the file accordingly, and move the geographically closest mirrors to the top of the list, although other criteria should be taken into account.

This file will later be copied to the new system by pacstrap, so it is worth getting right.

Install essential packages

Use the pacstrap(8) script to install the package, Linux kernel and firmware for common hardware:

# pacstrap -K /mnt base linux linux-firmware

The package does not include all tools from the live installation, so installing other packages may be necessary for a fully functional base system. In particular, consider installing:

  • userspace utilities for the management of file systems that will be used on the system,
  • utilities for accessing RAID or LVM partitions,
  • specific firmware for other devices not included in (e.g. for sound cards),
  • software necessary for networking (e.g. a network manager or DHCP client),
  • a text editor,
  • packages for accessing documentation in man and info pages: , man-pages and .

To install other packages or package groups, append the names to the pacstrap command above (space separated) or use pacman while chrooted into the new system. For comparison, packages available in the live system can be found in pkglist.x86_64.txt.

Configure the system


Generate an fstab file (use or to define by UUID or labels, respectively):

# genfstab -U /mnt >> /mnt/etc/fstab

Check the resulting file, and edit it in case of errors.


Change root into the new system:

# arch-chroot /mnt

Time zone

Set the time zone:

# ln -sf /usr/share/zoneinfo/Region/City /etc/localtime

Run to generate :

# hwclock --systohc

This command assumes the hardware clock is set to UTC. See System time#Time standard for details.


Edit and uncomment en_US.UTF-8 UTF-8 and other needed locales. Generate the locales by running:

# locale-gen

Create the file, and set the LANG variable accordingly:

If you set the console keyboard layout, make the changes persistent in vconsole.conf(5):

Network configuration

Create the hostname file:

Complete the network configuration for the newly installed environment. That may include installing suitable network management software.


Creating a new initramfs is usually not required, because mkinitcpio was run on installation of the kernel package with pacstrap.

For LVM, system encryption or RAID, modify and recreate the initramfs image:

# mkinitcpio -P

Root password

Set the root password:

# passwd

Boot loader

Choose and install a Linux-capable boot loader. If you have an Intel or AMD CPU, enable microcode updates in addition.


Exit the chroot environment by typing or pressing .

Optionally manually unmount all the partitions with : this allows noticing any "busy" partitions, and finding the cause with .

Finally, restart the machine by typing : any partitions still mounted will be automatically unmounted by systemd. Remember to remove the installation medium and then login into the new system with the root account.


See General recommendations for system management directions and post-installation tutorials (like creating unprivileged user accounts, setting up a graphical user interface, sound or a touchpad).

For a list of applications that may be of interest, see List of applications.

gollark: Unless you make the reactor building very big.
gollark: For wiring from the reactor to cells, we can afford most things.
gollark: So if you feed the reactor output straight into a cell and make the cell output into three fluxducts, you could have the actual long range wiring carry all the power, but each machine would only receive 1kRF/t max unless you have a bunch of connections on that machine.
gollark: Er, per terminal, not pair.
gollark: It's actually 1kRF/t per terminal pair.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.