Difference between revisions of "Beginners' guide"

From ArchWiki
Jump to: navigation, search
(Set the root password and add a regular user: Kill storage group.)
(Corrected for broken links)
 
Line 1: Line 1:
<noinclude>
 
 
[[Category:Getting and installing Arch]]
 
[[Category:Getting and installing Arch]]
[[Category:About Arch]]
+
[[ar:Beginners' guide]]
[[da:Beginners' Guide/Installation]]
+
[[bg:Beginners' guide]]
[[es:Beginners' Guide/Installation]]
+
[[cs:Beginners' guide]]
[[hr:Beginners' Guide/Installation]]
+
[[da:Beginners' guide]]
[[hu:Beginners' Guide/Installation]]
+
[[de:Anleitung für Einsteiger]]
[[it:Beginners' Guide/Installation]]
+
[[el:Beginners' guide]]
[[ja:Beginners' Guide/Installation]]
+
[[es:Beginners' guide]]
[[ko:Beginners' Guide/Installation]]
+
[[fa:راهنمای_تازه‌کاران]]
[[nl:Beginners' Guide/Installatie]]
+
[[fr:Installation]]
[[pl:Beginners' Guide/Installation]]
+
[[he:Beginners' guide]]
[[pt:Beginners' Guide/Installation]]
+
[[hr:Beginners' guide]]
[[ro:Ghidul începătorilor/Instalare]]
+
[[hu:Beginners' guide]]
[[ru:Beginners' Guide/Installation]]
+
[[id:Beginners' guide]]
[[sr:Beginners' Guide/Installation]]
+
[[it:Beginners' guide]]
[[zh-CN:Beginners' Guide/Installation]]
+
[[ja:ビギナーズガイド]]
{{Tip|This is part of a multi-page article for The Beginners' Guide. '''[[Beginners' Guide|Click here]]''' if you would rather read the guide in its entirety.}}
+
[[ko:Beginners' guide]]
</noinclude>
+
[[lt:Beginners' guide]]
== Installation ==
+
[[nl:Beginners' guide]]
 +
[[pl:Beginners' guide]]
 +
[[pt:Beginners' guide]]
 +
[[ro:Ghidul începătorilor]]
 +
[[ru:Beginners' guide]]
 +
[[sk:Beginners' guide]]
 +
[[sr:Beginners' guide]]
 +
[[sv:Nybörjarguiden]]
 +
[[tr:Yeni başlayanlar rehberi]]
 +
[[uk:Beginners' guide]]
 +
[[zh-cn:Beginners' guide]]
 +
[[zh-tw:Beginners' guide]]
 +
{{Related articles start}}
 +
{{Related|:Category:Accessibility}}
 +
{{Related|Help:Reading}}
 +
{{Related|Installation guide}}
 +
{{Related|General recommendations}}
 +
{{Related|General troubleshooting}}
 +
{{Related articles end}}
 +
This document will guide you through the process of installing [[Arch Linux]] using the [https://projects.archlinux.org/arch-install-scripts.git/ Arch Install Scripts]. Before installing, you are advised to skim over the [[FAQ]].
  
You are now presented with a shell prompt, automatically logged in as root.
+
The community-maintained [[Main page|ArchWiki]] is the primary resource that should be consulted if issues arise. The [[IRC channel]] (irc://irc.freenode.net/#archlinux) and the [https://bbs.archlinux.org/ forums] are also excellent resources if an answer cannot be found elsewhere. In accordance with [[the Arch Way]], you are encouraged to type {{ic|man ''command''}} to read the [[man page]] of any command you are unfamiliar with.
  
=== Change the language ===
+
== Preparation ==
  
{{Tip|These are optional for the majority of users. Useful only if you plan on writing in your own language in any of the configuration files, if you use diacritical marks in the Wi-Fi password, or if you would like to receive system messages (e.g. possible errors) in your own language.}}
+
Arch Linux should run on any [[Wikipedia:P6 (microarchitecture)|i686]] compatible machine with a minimum of 256 MB RAM. A basic installation with all packages from the {{Grp|base}} group should take less than 800 MB of disk space.
  
By default, the keyboard layout is set to {{ic|us}}. If you have a non-[[Wikipedia:File:KB United States-NoAltGr.svg|US]] keyboard layout, run:
+
See [[:Category:Getting and installing Arch]] for instructions on downloading the installation medium, and methods for booting it to the target machine(s). This guide assumes you use the latest available version.
  
# loadkeys ''layout''
+
== Boot the installation medium ==
  
...where ''layout'' can be {{ic|fr}}, {{ic|uk}}, {{ic|be-latin1}}, etc. See [[KEYMAP#Keyboard layouts|here]] for a comprehensive list.
+
Point the current boot device to the drive containing the Arch installation media. This is typically achieved by pressing a key during the [[Wikipedia:Power-on self test|POST]] phase, as indicated on the splash screen. Refer to your motherboard's manual for details.
  
The font should also be changed, because most languages use more glyphs than the 26 letter [[Wikipedia:English alphabet|English alphabet]]. Otherwise some foreign characters may show up as white squares or as other symbols. Note that the name is case-sensitive, so please type it ''exactly'' as you see it:
+
When the Arch menu appears, select ''Boot Arch Linux'' and press {{ic|Enter}} to enter the installation environment. See [https://projects.archlinux.org/archiso.git/tree/docs/README.bootparams README.bootparams] for a list of [[Kernel parameters#Configuration|boot parameters]].
  
# setfont Lat2-Terminus16
+
You will be logged in as the root user and presented with a [[Zsh]] shell prompt. ''Zsh'' provides advanced [http://zsh.sourceforge.net/Guide/zshguide06.html tab completion] and other features as part of the [http://grml.org/zsh/ grml config]. For [[create|modifying or creating]] configuration files, typically in {{ic|/etc}}, [[nano#Usage|nano]] and [[vim#Usage|vim]] are suggested.
  
By default, the language is set to English (US). If you would like to change the language for the install process ''(German, in this example)'', remove the {{ic|#}} in front of the [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 locale] you want from {{ic|/etc/locale.gen}}, along with English (US). Please choose the {{ic|UTF-8}} entry.
+
=== UEFI mode ===
  
Use {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.
+
In case you have a [[UEFI]] motherboard with UEFI mode enabled, the CD/USB will automatically launch Arch Linux via [http://www.freedesktop.org/wiki/Software/systemd/systemd-boot/ systemd-boot].
  
{{hc|# nano /etc/locale.gen|
+
To verify you are booted in UEFI mode, check that the following directory is populated:
en_US.UTF-8 UTF-8
+
de_DE.UTF-8 UTF-8}}
+
  
  # locale-gen
+
  # ls /sys/firmware/efi/efivars
# export LANG=de_DE.UTF-8
+
  
Remember, {{Keypress|LAlt+LShift}} activates and deactivates the keymap.
+
See [[UEFI#UEFI Variables]] for details.
  
=== Establish an internet connection ===
+
=== Set the keyboard layout ===
  
The {{ic|dhcpcd}} network daemon is started automatically at boot and it will attempt to start a wired connection, if available. Try pinging a website to see if it was successful. And since Google is always on...
+
The default [[Keyboard_configuration_in_console|console keymap]] is set to [[Wikipedia:File:KB United States-NoAltGr.svg|us]]. Available choices can be listed with {{ic|ls /usr/share/kbd/keymaps/**/*.map.gz}}.  
  
{{hc|# ping -c 3 www.google.com|2=
+
{{Note|{{ic|localectl list-keymaps}} does not work due to bug {{Bug|46725}}.}}
PING www.l.google.com (74.125.132.105) 56(84) bytes of data.
+
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=1 ttl=50 time=17.0 ms
+
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=2 ttl=50 time=18.2 ms
+
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=3 ttl=50 time=16.6 ms
+
  
--- www.l.google.com ping statistics ---
+
For example, to change the layout to {{ic|de-latin1}}, run:
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
+
rtt min/avg/max/mdev = 16.660/17.320/18.254/0.678 ms}}
+
  
If you get a {{ic|ping: unknown host}} error, you will need to set up the network manually, as explained below.
+
# loadkeys ''de-latin1''
  
Otherwise, move on to [[#Prepare the storage drive|Prepare the storage drive]].
+
If certain characters appear as white squares or other symbols, change the [[Console fonts|console font]]. For example:
  
==== Wired ====
+
# setfont ''lat9w-16''
  
Follow this procedure if you need to set up a wired connection via a static IP address.
+
=== Connect to the Internet ===
  
If your computer is connected to an Ethernet network, in most cases, you will have one interface, called {{ic|eth0}}. If you have additional network cards (apart from the one integrated on the motherboard, for example), their name will follow the sequence {{ic|eth1}}, {{ic|eth2}}, etc.
+
; Wired
  
You need to know these settings:
+
The [[dhcpcd]] daemon is enabled on boot for wired devices, and will attempt to start a connection. To access captive portal login forms, use the [[ELinks]] browser.
  
* Static IP address.
+
Verify a connection was established, for example with ''ping''. If none is available, proceed to [[Network configuration|configure the network]]; the examples below use [[netctl]] to this purpose. To prevent conflicts, [[stop]] the ''dhcpcd'' service (replacing {{ic|enp0s25}} with the correct wired interface):
* Subnet mask.
+
* Gateway's IP address.
+
* Name servers' (DNS) IP addresses.
+
* Domain name (unless you're on a local LAN, in which case you can make it up).
+
  
Activate the connected Ethernet interface (e.g. {{ic|eth0}}):
+
# systemctl stop dhcpcd@''enp0s25''.service
  
# ip link set eth0 up
+
[[Network configuration#Device names|Interfaces]] can be listed using {{ic|ip link}}, or {{ic|iw dev}} for wireless devices. They are prefixed with {{ic|en}} (ethernet), {{ic|wl}} (WLAN), or {{ic|ww}} (WWAN).
  
Add the address:
+
; Wireless
  
# ip addr add <ip address>/<subnetmask> dev <interface>
+
List [[Wireless_network_configuration#Getting_some_useful_information|available networks]], and make a connection for a specified interface:
  
For example:
+
# wifi-menu -o ''wlp2s0''
  
# ip addr add 192.168.1.2/24 dev eth0
+
The resulting configuration file is stored in {{ic|/etc/netctl}}. For networks which require both a username and password, see [[WPA2 Enterprise#netctl]].
  
For more options, run {{ic|man ip}}.
+
; Other
  
Add your gateway like this, substituting your own gateway's IP address:
+
Several example profiles, such as for configuring a [[Network configuration#Static IP address|static IP address]], are available. Copy the required one to {{ic|/etc/netctl}}, for example {{ic|ethernet-static}}:
  
  # ip route add default via <ip address>
+
  # cp /etc/netctl/examples/''ethernet-static'' /etc/netctl
  
For example:
+
Adjust the copy as needed, and enable it:
  
  # ip route add default via 192.168.1.1
+
  # netctl start ''ethernet-static''
  
Edit {{ic|resolv.conf}}, substituting your name servers' IP addresses and your local domain name:
+
=== Update the system clock ===
  
{{hc|# nano /etc/resolv.conf|
+
Use [[systemd-timesyncd]] to ensure that your system clock is accurate. To start it:
nameserver 61.23.173.5
+
nameserver 61.95.849.8
+
search example.com}}
+
  
{{Note|Currently, you may include a maximum of 3 {{ic|nameserver}} lines.}}
+
# timedatectl set-ntp true
  
You should now have a working network connection. If you do not, check the detailed [[Network Configuration]] page.
+
To check the service status, use {{ic|timedatectl status}}.
  
==== Wireless ====
+
== Prepare the storage devices ==
  
Follow this procedure if you need wireless connectivity (Wi-Fi) during the installation process.
+
{{Warning|
 +
* In general, partitioning or formatting will make existing data inaccessible and subject to being overwritten, i.e. destroyed, by subsequent operations. For this reason, all data that needs to be preserved must be backed up before proceeding.
 +
* If dual-booting with an existing installation of Windows on a UEFI/GPT system, avoid reformatting the UEFI partition, as this includes the Windows ''.efi'' file required to boot it. Furthermore, Arch must follow the same firmware boot mode and partitioning combination as Windows. See [[Dual boot with Windows#Important information]].}}
  
The wireless drivers and utilities are now available to you in the live environment of the installation media. A good knowledge of your wireless hardware will be of key importance to successful configuration. Note that the following quick-start procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment of the installation media''. These steps (or some other form of wireless management) '''must be repeated from the actual installed system after booting into it'''.
+
In this step, the storage devices that will be used by the new system will be prepared. Read [[Partitioning]] for a more general overview.
  
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.
+
Users intending to create stacked block devices for [[LVM]], [[disk encryption]] or [[RAID]], should keep those instructions in mind when preparing the partitions. If intending to install to a USB flash key, see [[Installing Arch Linux on a USB key]].
  
{{Note|The following examples use {{ic|wlan0}} for the interface and {{ic|linksys}} for the ESSID. Remember to change these values according to your setup.}}
+
=== Identify the devices ===
  
The basic procedure will be:
+
The first step is to identify the devices where the new system will be installed. The following command will show all the available devices:
  
* (optional) Identify the wireless interface:
+
# lsblk
  
# lspci | grep -i net
+
This will list all devices connected to your system along with their partition schemes, including that used to host and boot live Arch installation media (e.g. a USB drive). Not all devices listed will therefore be viable or appropriate mediums for installation. Results ending in {{ic|rom}}, {{ic|loop}} or {{ic|airoot}} can be ignored.
  
Or, if using a USB adapter:
+
Devices (e.g. hard disks) will be listed as {{ic|sd''x''}}, where {{ic|''x''}} is a lower-case letter starting from {{ic|a}} for the first device ({{ic|sda}}), {{ic|b}} for the second device ({{ic|sdb}}), and so on. Existing partitions on those devices will be listed as {{ic|sd''xY''}}, where {{ic|''Y''}} is a number starting from {{ic|1}} for the first partition, {{ic|2}} for the second, and so on. In the example below, only one device is available ({{ic|sda}}), and that device has only one partition ({{ic|sda1}}):
  
  # lsusb
+
  NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 +
sda              8:0    0    80G  0 disk
 +
└─sda1            8:1    0    80G  0 part
  
* Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with {{ic|iwconfig}}:
+
The {{ic|sd''xY''}} convention will be used in the examples provided below for partition tables, partitions, and file systems. As they are just examples, it is important to ensure that any necessary changes to device names, partition numbers, and/or partition sizes (etc.) are made. Do not just blindly copy and paste the commands.
  
{{Note|If you do not see output similar to this, then your wireless driver has not been loaded. If this is the case, you must load the driver yourself. Please see [[Wireless Setup]] for more detailed information.}}
+
If the existing partition scheme does not need to be changed, skip to [[#Format the file systems and enable swap]], otherwise continue reading the following section.
  
{{hc|# iwconfig|2=
+
=== Partition table types ===
lo no wireless extensions.
+
eth0 no wireless extensions.
+
wlan0    unassociated  ESSID:""
+
        Mode:Managed  Channel=0  Access Point: Not-Associated
+
        Bit Rate:0 kb/s  Tx-Power=20 dBm  Sensitivity=8/0
+
        Retry limit:7  RTS thr:off  Fragment thr:off
+
        Power Management:off
+
        Link Quality:0  Signal level:0  Noise level:0
+
        Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
+
        Tx excessive retries:0  Invalid misc:0  Missed beacon:0}}
+
  
In this example, {{ic|wlan0}} is the available wireless interface.
+
If you are installing alongside an existing installation (i.e. dual-booting), a partition table will already be in use. If the devices are not partitioned, or the current partitions table or scheme needs to be changed, you will first have to determine the partition tables (one for each device) in use or to be used.
  
* Bring the interface up with:
+
There are two types of partition table:
  
# ip link set wlan0 up
+
* [[GPT]]
 +
* [[MBR]]
  
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error when bringing the interface up:
+
Any existing partition table can be identified with the following command for each device:
  
{{hc|# ip link set wlan0 up|
+
# parted /dev/sd''x'' print
SIOCSIFFLAGS: No such file or directory}}
+
  
If unsure, invoke {{ic|dmesg}} to query the kernel log for a firmware request from the wireless chipset.
+
=== Partitioning tools ===
  
Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:
+
{{Warning|Using a partitioning tool that is incompatible with your partition table type will likely result in the destruction of that table, along with any existing partitions/data.}}
  
{{hc|# dmesg <nowiki>|</nowiki> grep firmware|
+
For each device to be partitioned, a proper tool must be chosen according to the partition table to be used. Several partitioning tools are provided by the Arch installation medium, including:
firmware: requesting iwlwifi-5000-1.ucode}}
+
  
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.
+
* [[parted]]: GPT and MBR
 +
* [[fdisk#Usage|fdisk]], '''cfdisk''', '''sfdisk''': GPT and MBR
 +
* [[gdisk|gdisk]], '''cgdisk''', '''sgdisk''': GPT
  
{{Warning|Wireless chipset firmware packages (for cards which require them) are pre-installed under {{ic|/usr/lib/firmware}} in the live environment (on CD/USB stick) '''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!''' Package installation is covered later in this guide. Ensure installation of both your wireless module and firmware before rebooting! See [[Wireless Setup]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset.}}
+
Devices may also be partitioned before booting the installation media, for example through tools such as [[GParted]] (also provided as a [http://gparted.sourceforge.net/livecd.php live CD]).
  
Next, use {{Pkg|netcfg}}'s {{ic|wifi-menu}} to connect to a network:
+
==== Using parted in interactive mode ====
  
# wifi-menu wlan0
+
All the examples provided below make use of ''parted'', as it can be used for both UEFI/GPT and BIOS/MBR. It will be launched in ''interactive mode'', which simplifies the partitioning process and reduces unnecessary repetition by automatically applying all partitioning commands to the specified device.
  
You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.
+
In order to start operating on a device, execute:
  
==== xDSL (PPPoE), analog modem or ISDN ====
+
# parted /dev/sd''x''
  
If you have a router in bridge mode, run:
+
You will notice that the command-line prompt changes from a hash ({{ic|#}}) to {{ic|(parted)}}: this also means that the new prompt is not a command to be manually entered when running the commands in the examples.
  
# pppoe-setup
+
To see a list of the available commands, enter:
  
* Type in the username that the ISP provided you with.
+
(parted) help
* Press {{Keypress|Enter}} for "eth0".
+
* Press {{Keypress|Enter}} for "no", so that it stays up continuously.
+
* Type {{ic|server}} (since this is usually the case).
+
* Press {{Keypress|1}} for a firewall.
+
* Type in the password that the ISP provided you with.
+
* Press {{Keypress|Y}} at the end.
+
  
To use these settings and connect to your ISP, run:
+
When finished, or if wishing to implement a partition table or scheme for another device, exit from parted with:
  
  # pppoe-start
+
  (parted) quit
  
You may also need to adjust your {{ic|resolv.conf}}:
+
After exiting, the command-line prompt will change back to {{ic|#}}.
  
# echo nameserver 8.8.8.8 > /etc/resolv.conf
+
=== Create new partition table ===
  
If you have a dial-up or ISDN connection, see [[Direct Modem Connection]].
+
You need to (re)create the partition table of a device when it has never been partitioned before, or when you want to change the type of its partition table. Recreating the partition table of a device is also useful when the partition scheme needs to be restructured from scratch.
  
==== Behind a proxy server ====
+
Open each device whose partition table must be (re)created with:
  
If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}} environment variables. See [[Proxy settings]] for more information.
+
# parted /dev/sd''x''
  
=== Prepare the storage drive ===
+
To then create a new GPT partition table for UEFI systems, use the following command:
  
{{Warning|Partitioning can destroy data. You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}
+
(parted) mklabel gpt
  
Absolute beginners are encouraged to use a graphical partitioning tool. [http://gparted.sourceforge.net/download.php GParted] is a good example, and is [http://gparted.sourceforge.net/livecd.php provided as a "live" CD]. It is also included on live CDs of most Linux distributions such as [[Wikipedia:Ubuntu (operating system)|Ubuntu]] and [[Wikipedia:Linux Mint|Linux Mint]]. A drive should first be [[partitioning|partitioned]] and the partitions should be formatted with a [[File Systems|file system]] before rebooting.
+
To create a new MBR/msdos partition table for BIOS systems instead, use:
  
It's possible to set up a swap file at any point after installation, so there is no need to decide on swap size now. See [[Swap]] for details if you wish to set up a swap partition now (but note that it's much easier to resize a file than a partition).
+
(parted) mklabel msdos
  
If you have already done so, proceed to [[#Mount the partitions|Mount the partitions]].
+
=== Partition schemes ===
  
Otherwise, see the following example.
+
You can decide the number and size of the partitions the devices should be split into, and which directories will be used to mount the partitions in the installed system (also known as ''mount points''). The mapping from partitions to directories is the [[Partitioning#Partition scheme|partition scheme]], which must comply with the following requirements:
  
==== Example ====
+
* At least a partition for the {{ic|/}} (''root'') directory '''must''' be created.
 +
* When using a UEFI motherboard, one [[EFI System Partition]] '''must''' be created.
  
The Arch Linux install media includes the following partitioning tools:
+
In the examples below it is assumed that a new and contiguous partitioning scheme is applied to a single device. Some optional partitions will also be created for the {{ic|/boot}} and {{ic|/home}} directories which otherwise would simply be contained in the {{ic|/}} partition. See the [[Arch filesystem hierarchy]] for an explanation of the purpose of the various directories. Also the creation of an optional partiton for [[swap space]] will be illustrated.
  
* [[Wikipedia:gdisk|gdisk]] and [[Wikipedia:cgdisk|cgdisk]] – support only [[GPT]] partition tables.
+
If not already open in a ''parted'' interactive session, open each device to be partitioned with:
  
* [[Wikipedia:fdisk|fdisk]] and [[Wikipedia:cfdisk|cfdisk]] – support only [[MBR]] partition tables.
+
# parted /dev/sd''x''
  
* [[Wikipedia:GNU Parted|parted]] – supports both.
+
The following command will be used to create partitions:
  
This example uses '''cfdisk''', but it can easily be followed using '''cgdisk''', which will allow for GPT instead of MBR partitioning.
+
(parted) mkpart ''part-type'' ''fs-type'' ''start'' ''end''
  
{{Box BLUE|Notes regarding [[UEFI]] boot:|
+
* {{ic|''part-type''}} is one of {{ic|primary}}, {{ic|extended}} or {{ic|logical}}, and is meaningful only for MBR partition tables.
* If you have a UEFI motherboard, you will need to create an extra [[Unified Extensible Firmware Interface#Create an UEFI System Partition_in_Linux|UEFI System partition]].
+
* {{ic|''fs-type''}} is an identifier chosen among those listed by entering {{ic|help mkpart}} as the closest match to the file system that you will use in [[#Format the file systems and enable swap]]. The ''mkpart'' command does not actually create the file system: the {{ic|''fs-type''}} parameter will simply be used by ''parted'' to set a 1-byte code that is used by boot loaders to "preview" what kind of data is found in the partition, and act accordingly if necessary. See also [[Wikipedia:Disk partitioning#PC partition types]].
* It is recommended to always use GPT for UEFI boot, as some UEFI firmwares do not allow UEFI-MBR boot.}}
+
: {{Tip|Most [[Wikipedia:File_system#Linux|Linux native file systems]] map to the same partition code ([[Wikipedia:Partition type#PID_83h|0x83]]), so it is perfectly safe to e.g. use {{ic|ext2}} for an ''ext4''-formatted partition.}}
 +
* {{ic|''start''}} is the beginning of the partition from the start of the device. It consists of a number followed by a [http://www.gnu.org/software/parted/manual/parted.html#unit unit], for example {{ic|1M}} means start at 1MiB.
 +
* {{ic|''end''}} is the end of the partition from the start of the device (''not'' from the {{ic|''start''}} value). It has the same syntax as {{ic|''start''}}, for example {{ic|100%}} means end at the end of the device (use all the remaining space).
  
{{Box BLUE|Notes regarding [[GPT]] partitioning:|
+
{{Warning|It is important that the partitions do not overlap each other: if you do not want to leave unused space in the device, make sure that each partition starts where the previous one ends.}}
* If you are not dual booting with Windows, then it is advisable to use GPT instead of MBR. Read [[GPT]] for a list of advantages.
+
* If you have a BIOS motherboard (or plan on booting in BIOS compatibility mode) and you want to setup GRUB on a GPT-partitioned drive, you will need to create a 2 MiB "[[GRUB#GPT specific instructions|BIOS Boot Partition]]". Syslinux doesn't need one.
+
* Some BIOS systems may have issues with GPT. See http://mjg59.dreamwidth.org/8035.html and http://rodsbooks.com/gdisk/bios.html for more info and possible workarounds.}}
+
  
{{Note|If you are installing to a USB flash key, see [[Installing Arch Linux on a USB key]].}}
+
{{Note|''parted'' may issue a warning like:
  
  # cfdisk /dev/sda
+
  Warning: The resulting partition is not properly aligned for best performance.
 +
Ignore/Cancel?
  
The example system will contain a 15 GB root partition, and a [[Partitioning#/home|home]] partition for the remaining space.
+
In this case, read [[Partitioning#Partition alignment]] and follow [[GNU Parted#Alignment]] to fix it.}}
  
It should be emphasized that partitioning is a personal choice and that this example is only for illustrative purposes. See [[Partitioning]].
+
The following command will be used to flag the partition that contains the {{ic|/boot}} directory as bootable:
  
'''Root:'''
+
(parted) set ''partition'' boot on
  
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – type in "15360" – {{Keypress|Enter}} for Beginning – {{Keypress|Enter}} for Bootable.
+
* {{ic|''partition''}} is the number of the partition to be flagged (see the output of the {{ic|print}} command).
  
'''Home:'''
+
==== UEFI/GPT examples ====
  
* Press the down arrow to move to the free space area.
+
In every instance, a special bootable [[EFI System Partition]] is required.
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – {{Keypress|Enter}} to use the rest of the drive (or you could type in the desired size).
+
  
Here's how it should look like:
+
If creating a new EFI System Partition, use the following commands (a size of 512MiB is suggested):
  
  Name    Flags    Part Type    FS Type          [Label]      Size (MB)
+
  (parted) mkpart ESP fat32 1MiB 513MiB
  -----------------------------------------------------------------------
+
  (parted) set 1 boot on
sda1    Boot      Primary    Linux                            15360
+
sda2              Primary    Linux                            133000*
+
  
Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.
+
The remaining partition scheme is entirely up to you. For one other partition using 100% of remaining space:
  
If you would like to start over, you can simply select Quit (or press {{Keypress|Q}}) to exit without saving changes and then restart cfdisk.
+
(parted) mkpart primary ext4 513MiB 100%
  
If you are satisfied, choose Write (or press {{Keypress|Shift+W}}) to finalize and to write the partition table to the drive. Type "yes" and choose Quit (or press {{Keypress|Q}}) to exit cfdisk without making any more changes.
+
For separate {{ic|/}} (20GiB) and {{ic|/home}} (all remaining space) partitions:
  
Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:
+
(parted) mkpart primary ext4 513MiB 20.5GiB
 +
(parted) mkpart primary ext4 20.5GiB 100%
  
{{Warning|Double check and triple check that it's actually {{ic|/dev/sda1}} and {{ic|/dev/sda2}} that you want to format.}}
+
And for separate {{ic|/}} (20GiB), swap (4GiB), and {{ic|/home}} (all remaining space) partitions:
  
  # mkfs.ext4 /dev/sda1
+
  (parted) mkpart primary ext4 513MiB 20.5GiB
  # mkfs.ext4 /dev/sda2
+
  (parted) mkpart primary linux-swap 20.5GiB 24.5GiB
 +
(parted) mkpart primary ext4 24.5GiB 100%
  
If you have made a partition dedicated to swap (code 82), don't forget to format and activate it with:
+
==== BIOS/MBR examples ====
  
# mkswap /dev/sda''X''
+
For a minimum single primary partition using all available disk space, the following command would be used:
# swapon /dev/sda''X''
+
  
=== Mount the partitions ===
+
(parted) mkpart primary ext4 1MiB 100%
 +
(parted) set 1 boot on
  
Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive.
+
In the following instance, a 20GiB {{ic|/}} partition will be created, followed by a {{ic|/home}} partition using all the remaining space:
  
To display the current partition layout:
+
(parted) mkpart primary ext4 1MiB 20GiB
 +
(parted) set 1 boot on
 +
(parted) mkpart primary ext4 20GiB 100%
  
# lsblk /dev/sda
+
In the final example below, separate {{ic|/boot}} (100MiB), {{ic|/}} (20GiB), swap (4GiB), and {{ic|/home}} (all remaining space) partitions will be created:
  
Pay attention, because the mounting order is important.
+
(parted) mkpart primary ext4 1MiB 100MiB
 +
(parted) set 1 boot on
 +
(parted) mkpart primary ext4 100MiB 20GiB
 +
(parted) mkpart primary linux-swap 20GiB 24GiB
 +
(parted) mkpart primary ext4 24GiB 100%
  
First, mount the root partition on {{ic|/mnt}}. Following the example above (yours may be different), it would be:
+
=== Format the file systems and enable swap ===
  
# mount /dev/sda1 /mnt
+
Once the partitions have been created, each '''must''' be formatted with an appropriate [[file system]], ''except'' for swap partitions. All available partitions on the intended installation device can be listed with the following command:
  
Then mount the {{ic|/home}} partition and any other separate partition ({{ic|/boot}}, {{ic|/var}}, etc), if you have any:
+
# lsblk /dev/sd''x''
  
# mkdir /mnt/home
+
With the exceptions noted below, it is recommended to use the {{ic|ext4}} file system:
# mount /dev/sda2 /mnt/home
+
  
In case you have a UEFI motherboard, mount the UEFI partition:
+
# mkfs.ext4 /dev/sd''xY''
  
# mkdir /mnt/boot/efi
+
''If'' a swap partition has been created, it must be set up and activated with:
# mount /dev/sda''X'' /mnt/boot/efi
+
  
=== Select a mirror ===
+
# mkswap /dev/sd''xY''
 +
# swapon /dev/sd''xY''
  
Before installing, you may want to edit the {{ic|mirrorlist}} file and place your preferred mirror first. A copy of this file will be installed on your new system by {{ic|pacstrap}} as well, so it's worth getting it right.
+
Mount the root partition to the {{ic|/mnt}} directory of the live system:
  
{{hc|# nano /etc/pacman.d/mirrorlist|
+
# mount /dev/sd''xY'' /mnt
##
+
## Arch Linux repository mirrorlist
+
## Sorted by mirror score from mirror status page
+
## Generated on 2012-MM-DD
+
##
+
  
<nowiki>Server = http://mirror.example.xyz/archlinux/$repo/os/$arch</nowiki>
+
Remaining [[Partitioning#Partition_scheme|partitions]] (except ''swap'') may be mounted in any order, after creating the respective mount points. For example, when using a {{ic|/boot}} partition:
...}}
+
  
* {{Keypress|Alt+6}} to copy a {{ic|Server}} line.
+
# mkdir -p /mnt/boot
* {{Keypress|PageUp}} key to scroll up.
+
# mount /dev/sd''xZ'' /mnt/boot
* {{Keypress|Ctrl+U}} to paste it at the top of the list.
+
* {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.
+
  
If you want, you can make it the ''only'' mirror available by getting rid of everything else (using {{Keypress|Ctrl+K}}), but it's usually a good idea to have a few more, in case the first one goes offline.
+
''If'' a new UEFI system partition has been created on a UEFI/GPT system, it '''must''' be formatted with a {{ic|fat32}} file system:
  
{{Tip|
+
# mkfs.fat -F32 /dev/sd''xY''
* Use the [https://www.archlinux.org/mirrorlist/ Mirrorlist Generator] to get an updated list for your country. HTTP mirrors are faster than FTP, because of something called [[Wikipedia:Keepalive|keepalive]]. With FTP, pacman has to send out a signal each time it downloads a package, resulting in a brief pause. For other ways to generate a mirror list, see [[Mirrors#Sorting mirrors|Sorting mirrors]] and [[Reflector]].
+
* [https://archlinux.org/mirrors/status/ Arch Linux MirrorStatus] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.}}
+
  
{{Note|
+
{{ic|/mnt/boot}} is also recommended for mounting the (formatted or already existing) EFI System Partition on a UEFI/GPT system. See [[EFISTUB]] and related articles for alternatives.
* Whenever in the future you change your list of mirrors, always remember to force pacman to refresh all package lists with {{ic|pacman -Syy}}. This is considered to be good practice and will avoid possible headaches. See [[Mirrors]] for more information.
+
* If you're using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see {{Bug|22510}}). Therefore it is advised to obtain the latest mirror information as described above.
+
* Some issues have been reported in the [https://bbs.archlinux.org/ Arch Linux forums] regarding network problems that prevent pacman from updating/synchronizing repositories (see [https://bbs.archlinux.org/viewtopic.php?id&#61;68944] and [https://bbs.archlinux.org/viewtopic.php?id&#61;65728]). When installing Arch Linux natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see [[Improve Pacman Performance]] for more details). When installing Arch Linux as a guest OS in [[VirtualBox]], this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.}}
+
  
=== Install the base system ===
+
== Installation ==
  
The base system is installed using the [https://github.com/falconindy/arch-install-scripts/blob/master/pacstrap.in pacstrap] script.
+
=== Select the mirrors ===
  
The {{ic|-i}} switch can be omitted if you wish to install every package from the ''base'' and ''base-devel'' groups without prompting.
+
Packages to be installed must be downloaded from mirror servers, which are defined in {{ic|/etc/pacman.d/mirrorlist}}. On the live system, all mirrors are enabled, and sorted by their synchronization status and speed at the time the installation image was created.
  
# pacstrap -i /mnt base base-devel
+
The higher a mirror is placed in the list, the more priority it is given when downloading a package. You may want to edit the file accordingly, and move the geographically closest mirrors to the top of the list, although other criteria should be taken into account. See [[Mirrors]] for details.
  
{{Note|If pacman fails to verify your packages, check the system time with {{ic|cal}}. If the system date is invalid (e.g. it shows year 2010), signing keys will be considered expired (or invalid), signature checks on packages will fail and installation will be interrupted. Make sure to correct the system time, either by doing so manually or with the {{Pkg|ntp}} client, and retry running the pacstrap command. Refer to [[Time]] page for more information on correcting system time.}}
+
''pacstrap'' will also install a copy of this file to the new system, so it is worth getting right.
  
* {{Grp|base}}: Software packages from the [core] repo to provide the minimal base environment.
+
=== Install the base packages ===
  
* {{Grp|base-devel}}: Extra tools from [core] such as {{ic|make}}, and {{ic|automake}}. Most beginners should choose to install it, as it will likely be needed to expand the system. The ''base-devel'' group will be required to install software from the [[Arch User Repository]].
+
The ''pacstrap'' script installs the base system. To build packages from the [[AUR]] or with [[ABS]], the {{Grp|base-devel}} group is also required.
  
This will give you a basic Arch system. Other packages can be installed later using [[pacman]].
+
Not all tools from the live installation (see [https://projects.archlinux.org/archiso.git/tree/configs/releng/packages.both packages.both]) are part of the base group. Packages can later be [[install]]ed with ''pacman'', or by appending their names to the ''pacstrap'' command.
  
=== Generate an fstab ===
+
# pacstrap -i /mnt base base-devel
  
Generate an [[fstab]] file with the following command. UUIDs will be used because they have certain advantages (see [[fstab#Identifying filesystems]]). If you would prefer to use labels instead, replace the {{ic|-U}} option with {{ic|-L}}.
+
The {{ic|-i}} switch ensures prompting before package installation.
  
{{Note|If you encounter errors running genfstab or later in the install process, do '''not''' run genfstab again; just edit the fstab file.}}
+
== Configuration ==
  
# genfstab -U -p /mnt >> /mnt/etc/fstab
+
=== fstab ===
# nano /mnt/etc/fstab
+
  
{{Warning|The fstab file should always be checked after generating it. If you made an EFI system partition earlier, then {{ic|genfstab}} has incorrectly added options to your EFI system partition. This will in fact ''prevent'' your computer from booting from that drive, so you need to remove all options for the EFI partition except for {{ic|noatime}}. For the other partitions that use it, be sure to replace {{ic|1="codepage=cp437"}} with {{ic|1="codepage=437"}} or else when you next reboot, any mounts with this option will fail and systemd will halt and drop into recovery mode. This should be fixed by linux 3.8}}
+
Generate an [[fstab]] file. The {{ic|-U}} option indicates UUIDs: see [[Persistent block device naming]]. Labels can be used instead through the {{ic|-L}} option.
  
A few considerations:
+
# genfstab -U /mnt >> /mnt/etc/fstab
  
* Please take the time to align the columns properly, using spaces and the {{Keypress|Tab}} key, like in the examples from the [[fstab]] page. This way it's easier to read and also easier to spot a potential problem.
+
Check the resulting file in {{ic|/mnt/etc/fstab}} afterwards, and edit it in case of errors.
* Only the root ({{ic|/}}) partition needs {{ic|1}} for the last field. Everything else should have either {{ic|2}} or {{ic|0}} (see [[fstab#Field definitions]]).
+
* The {{ic|1=data=ordered}} option can be removed, because it will be used automatically whether you specify it or not. No point in cluttering up your fstab.
+
* Though its presence will not do any harm, you may remove the {{ic|tmpfs}} entry, as this is now handled by systemd's {{ic|tmp.mount}} unit. To disable it, you must remove the fstab line and run:
+
: {{bc|# systemctl mask tmp.mount}}
+
  
=== Chroot and configure the base system ===
+
=== Change root ===
  
Next, we [[chroot]] into our newly installed system:
+
Copy netctl profiles in {{ic|/etc/netctl}} to the new system in {{ic|/mnt}} (when applicable), then [[chroot]] to it:
  
  # arch-chroot /mnt
+
  # arch-chroot /mnt /bin/bash
  
{{Note|Use {{ic|arch-chroot /mnt /bin/bash}} to chroot into a bash shell.}}
+
=== Locale ===
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system. These can either be created if they do not exist, or edited if you wish to change the defaults.
+
  
Closely following and understanding these steps is of key importance to ensure a properly configured system.
+
The [[Locale]] defines which language the system uses, and other regional considerations such as currency denomination, numerology, and character sets.
  
==== Locale ====
+
Possible values are listed in {{ic|/etc/locale.gen}}. Uncomment {{ic|en_US.UTF-8 UTF-8}}, as well as other needed localisations. Save the file, and generate the new locales:
 
+
Locales are used by '''glibc''' and other locale-aware programs or libraries for rendering text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.
+
 
+
There are two files that need editing: {{ic|locale.gen}} and {{ic|locale.conf}}.
+
 
+
* The {{ic|locale.gen}} file is empty by default (everything is commented out) and you need to remove the {{ic|#}} in front of the line(s) you want. You may uncomment more lines than just English (US), as long as you choose their {{ic|UTF-8}} encoding:
+
 
+
{{hc|# nano /etc/locale.gen|
+
en_US.UTF-8 UTF-8
+
de_DE.UTF-8 UTF-8}}
+
  
 
  # locale-gen
 
  # locale-gen
  
This will run on every '''glibc''' upgrade, generating all the locales specified in {{ic|/etc/locale.gen}}.
+
[[Create]] {{ic|/etc/locale.conf}}, where {{ic|LANG}} refers to the ''first column'' of an uncommented entry in {{ic|/etc/locale.gen}}:
  
* The {{ic|locale.conf}} file doesn't exist by default. Setting only {{ic|LANG}} should be enough. It will act as the default value for all other variables.
+
{{hc|1=/etc/locale.conf|2=
 
+
LANG=''en_US.UTF-8''
# echo LANG=en_US.UTF-8 > /etc/locale.conf
+
# export LANG=en_US.UTF-8
+
 
+
{{Note|If you set some other language than English at the beginning of the install, the above commands would be something like:
+
# echo LANG<nowiki>=</nowiki>de_DE.UTF-8 > /etc/locale.conf
+
# export LANG<nowiki>=</nowiki>de_DE.UTF-8
+
 
}}
 
}}
  
To use other {{ic|LC_*}} variables, first run {{ic|locale}} to see the available options. An advanced example can be found [[Locale#Setting_system-wide_locale|here]].
+
If you [[#Set the keyboard layout|set the keyboard layout]], make the changes persistent in {{ic|/etc/vconsole.conf}}. For example, if {{ic|de-latin1}} was set with ''loadkeys'', and {{ic|lat9w-16}} with ''setfont'', assign the {{ic|KEYMAP}} and {{ic|FONT}} variables accordingly:
 
+
{{Warning|Using the {{ic|LC_ALL}} variable is strongly discouraged because it overrides everything.}}
+
 
+
==== Console font and keymap ====
+
 
+
If you set a keymap at [[#Change_the_language|the beginning]] of the install process, load it now, as well, because the environment has changed. For example:
+
 
+
# loadkeys ''de-latin1''
+
# setfont Lat2-Terminus16
+
 
+
To make them available after reboot, edit {{ic|vconsole.conf}}:
+
  
{{hc|# nano /etc/vconsole.conf|2=
+
{{hc|1=/etc/vconsole.conf|2=
KEYMAP=de-latin1
+
KEYMAP=''de-latin1''
FONT=Lat2-Terminus16
+
FONT=''lat9w-16''
 
}}
 
}}
  
* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.
+
=== Time ===
  
* {{ic|FONT}} – Available alternate console fonts reside in {{ic|/usr/share/kbd/consolefonts/}}. The default (blank) is safe, but some foreign characters may show up as white squares or as other symbols. It's recommended that you change it to {{ic|Lat2-Terminus16}}, because according to {{ic|/usr/share/kbd/consolefonts/README.Lat2-Terminus16}}, it claims to support "about 110 language sets".
+
Select a [[time zone]]:
  
* Possible option {{ic|FONT_MAP}} – Defines the console map to load at boot. Read {{ic|man setfont}}. Removing it or leaving it blank is safe.
+
# tzselect
  
See [[Fonts#Console_fonts|Console fonts]] and {{ic|man vconsole.conf}} for more information.
+
Create the symbolic link {{ic|/etc/localtime}}, where {{ic|Zone/Subzone}} is the {{ic|TZ}} value from ''tzselect'':
  
==== Time zone ====
+
# ln -s /usr/share/zoneinfo/''Zone''/''SubZone'' /etc/localtime
  
Available time zones and subzones can be found in the {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} directories.
+
It is recommended to adjust the time skew, and set the time standard to UTC:
  
To view the available <Zone>, check the directory {{ic|/usr/share/zoneinfo/}}:
+
# hwclock --systohc --utc
  
# ls /usr/share/zoneinfo/
+
If other operating systems are installed on the machine, they must be configured accordingly. See [[Time]] for details.
  
Similarly, you can check the contents of directories belonging to a <SubZone>:
+
=== Initramfs ===
  
# ls /usr/share/zoneinfo/Europe
+
As [[mkinitcpio]] was run on installation of {{Pkg|linux}} with ''pacstrap'', most users can use the defaults provided in {{ic|mkinitcpio.conf}}.
  
Create a symbolic link {{ic|/etc/localtime}} to your zone file {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} using this command:
+
For special configurations, set the correct [[Mkinitcpio#HOOKS|hooks]] in {{ic|/etc/mkinitcpio.conf}} and [[Mkinitcpio#Image_creation_and_activation|re-generate]] the initramfs image:
  
  # ln -s /usr/share/zoneinfo/<Zone>/<SubZone> /etc/localtime
+
  # mkinitcpio -p linux
  
'''Example:'''
+
=== Install a boot loader ===
  
# ln -s /usr/share/zoneinfo/Europe/Minsk /etc/localtime
+
See [[Boot loaders]] for available choices and configurations. If you have an Intel CPU, install the {{Pkg|intel-ucode}} package, and [[Microcode#Enabling_Intel_microcode_updates|enable microcode updates]].
  
==== Hardware clock ====
+
==== UEFI/GPT ====
  
Set the hardware clock mode uniformly between your operating systems. Otherwise, they may overwrite the hardware clock and cause time shifts.
+
Here, the installation drive is assumed to be GPT-partioned, and have the [[EFI System Partition|EFI System Partition]] (gdisk type {{ic|EF00}}, formatted with FAT32) mounted at {{ic|/boot}}.
  
You can generate {{ic|/etc/adjtime}} automatically by using one of the following commands:
+
Install [[systemd-boot]] to the EFI system partition:
  
* '''UTC''' (recommended)
+
# bootctl install
  
: {{Note|Using [[Wikipedia:Coordinated Universal Time|UTC]] for the hardware clock does not mean that software will display time in UTC.}}
+
When successful, create a boot entry as described in [[systemd-boot#Configuration]] (replacing {{ic|$esp}} with {{ic|/boot}}), or adapt the examples in {{ic|/usr/share/systemd/bootctl/}}.
  
: {{bc|# hwclock --systohc --utc}}
+
==== BIOS/MBR ====
  
To synchronize your "UTC" time over the internet, see [[Network Time Protocol daemon|NTPd]].
+
Install the {{Pkg|grub}} package. To search for other operating systems, also install {{Pkg|os-prober}}:
  
* '''localtime''' (discouraged; used by default in Windows)
+
# pacman -S grub os-prober
  
: {{Warning|Using ''localtime'' may lead to several known and unfixable bugs. However, there are no plans to drop support for ''localtime''.}}
+
Install the bootloader to the ''drive'' Arch was installed to:
  
: {{bc|# hwclock --systohc --localtime}}
+
# grub-install --target=i386-pc ''/dev/sda''
  
If you have (or planning on having) a dual boot setup with Windows:
+
Generate {{ic|grub.cfg}}:
  
* Recommended: Set both Arch Linux and Windows to use UTC. A quick [[Time#UTC in Windows|registry fix]] is needed. Also, be sure to prevent Windows from synchronizing the time on-line, because the hardware clock will default back to ''localtime''.  
+
# grub-mkconfig -o /boot/grub/grub.cfg
  
* Not recommended: Set Arch Linux to ''localtime'' and disable any time-related services, like [[Network Time Protocol daemon|NTPd]] . This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when [[Wikipedia:Daylight saving time|DST]] kicks in. So please don't ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.
+
See [[GRUB]] for more information.
  
==== Kernel modules ====
+
=== Configure the network ===
  
{{Tip|This is just an example, you do not need to set it. All needed modules are automatically loaded by udev, so you will rarely need to add something here. Only add modules that you know are missing.}}
+
The procedure is similar to [[#Connect to the Internet]], except made persistent for subsequent boots. Select '''one''' daemon to handle the network.
 
+
For kernel modules to load during boot, place a {{ic|*.conf}} file in {{ic|/etc/modules-load.d/}}, with a name based on the program that uses them.
+
 
+
{{hc|# nano /etc/modules-load.d/virtio-net.conf|
+
# Load 'virtio-net.ko' at boot.
+
 
+
virtio-net}}
+
 
+
If there are more modules to load per {{ic|*.conf}}, the module names can be separated by newlines. A good example are the [[VirtualBox#Arch Linux guests|VirtualBox Guest Additions]].
+
 
+
Empty lines and lines starting with {{ic|#}} or {{ic|;}} are ignored.
+
  
 
==== Hostname ====
 
==== Hostname ====
  
Set the [[Wikipedia:hostname|hostname]] to your liking (e.g. ''arch''):
+
Set the [[hostname]] to your liking by [[add]]ing ''myhostname'' to the following file, where ''myhostname'' is the hostname you wish to set:
  
# echo ''myhostname'' > /etc/hostname
+
{{hc|1=/etc/hostname|2=
 +
''myhostname''
 +
}}
  
{{Note|You no longer need to edit {{ic|/etc/hosts}}. The {{Pkg|nss-myhostname}} package will provide host name resolution, and is installed on all systems by default.}}
+
It is recommended to [[append]] the same hostname to {{ic|localhost}} entries in {{ic|/etc/hosts}}. See [[Network configuration#Set the hostname]] for details.
 
+
=== Configure the network ===
+
 
+
You need to configure the network again, but this time for your newly installed environment. The procedure and prerequisites are very similar to the one described [[#Establish an internet connection|above]], except we are going to make it persistent and automatically run at boot.
+
 
+
{{Note|For more in-depth information on network configration, visit [[Configuring Network]] and [[Wireless Setup]].}}
+
  
 
==== Wired ====
 
==== Wired ====
  
; Dynamic IP
+
When only requiring a single wired connection, [[enable]] the [[dhcpcd]] service:
  
If you only use a single fixed wired network connection, you do not need a network management service and can simply enable the {{ic|dhcpcd}} service:
+
# systemctl enable dhcpcd@''interface''.service
  
# systemctl enable dhcpcd@eth0.service
+
Where {{ic|''interface''}} is an ethernet [[Network_configuration#Device_names|device name]].
  
Alternatively, you can use {{Pkg|netcfg}}'s {{ic|net-auto-wired}}, which gracefully handles dynamic connections to new networks:
+
See [[Network configuration#Configure the IP address]] for other available methods.
 
+
Install {{Pkg|ifplugd}}, which is required for {{ic|net-auto-wired}}:
+
 
+
# pacman -S ifplugd
+
 
+
Set up the dhcp profile and enable the {{ic|net-auto-wired}} service:
+
 
+
# cd /etc/network.d
+
# ln -s examples/ethernet-dhcp .
+
# systemctl enable net-auto-wired.service
+
 
+
; Static IP
+
 
+
Install {{Pkg|ifplugd}}, which is required for {{ic|net-auto-wired}}:
+
 
+
# pacman -S ifplugd
+
 
+
Copy a sample profile from {{ic|/etc/network.d/examples}} to {{ic|/etc/network.d}}:
+
 
+
# cd /etc/network.d
+
# cp examples/ethernet-static .
+
 
+
Edit the profile as needed:
+
 
+
# nano ethernet-static
+
 
+
Enable the {{ic|net-auto-wired}} service:
+
 
+
# systemctl enable net-auto-wired.service
+
  
 
==== Wireless ====
 
==== Wireless ====
  
You will need to install additional programs to be able to configure and manage wireless network profiles for [[netcfg]].
+
Install {{Pkg|iw}}, {{Pkg|wpa_supplicant}}, and (for ''wifi-menu'') {{Pkg|dialog}}:
  
[[NetworkManager]] and [[Wicd]] are other popular alternatives.
+
# pacman -S iw wpa_supplicant dialog
  
* Install the required packages:
+
Additional [[Wireless#Installing driver/firmware|firmware packages]] may also be required.
  
# pacman -S wireless_tools wpa_supplicant wpa_actiond dialog
+
If you used ''wifi-menu'' priorly, repeat the steps '''after''' finishing the rest of this installation and rebooting, to prevent conflicts with the existing processes.
  
If your wireless adapter requires a firmware (as described in the above [[#Wireless|Establish an internet connection]] section and also [[Wireless Setup#Drivers and firmware|here]]), install the package containing your firmware. For example:
+
See [[Netctl]] and [[Wireless#Wireless management]] for more information.
  
# pacman -S zd1211-firmware
+
=== Root password ===
  
* Connect to the network with {{ic|wifi-menu}} (optionally checking the interface name with {{ic|ip link}}, but usually it's {{ic|wlan0}}), which will generate a profile file in {{ic|/etc/network.d}} named after the SSID. There are also templates available in {{ic|/etc/network.d/examples/}} for manual configuration.
+
Set the root [[password]] with:
 
+
# wifi-menu
+
 
+
* Enable the {{ic|net-auto-wireless}} service, which will connect to known networks and gracefully handle roaming and disconnects:
+
 
+
# systemctl enable net-auto-wireless.service
+
 
+
{{Note|[[Netcfg]] also provides {{ic|net-auto-wired}}, which can be used in conjunction with {{ic|net-auto-wireless}}.}}
+
 
+
* Make sure that the correct wireless interface (usually {{ic|wlan0}}) is set in {{ic|/etc/conf.d/netcfg}}:
+
 
+
{{hc|# nano /etc/conf.d/netcfg|2=
+
WIRELESS_INTERFACE="wlan0"}}
+
 
+
It is also possible to define a list of network profiles that should be automatically connected, using the {{ic|AUTO_PROFILES}} variable in {{ic|/etc/conf.d/netcfg}}. If {{ic|AUTO_PROFILES}} is not set, all known wireless networks will be tried.
+
 
+
==== xDSL (PPPoE), analog modem or ISDN ====
+
 
+
For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].
+
 
+
=== Configure pacman ===
+
 
+
Pacman is the Arch Linux '''pac'''kage '''man'''ager. It is highly recommended to study and learn how to use it. Read {{ic|man pacman}}, have a look at the [[pacman]] article, or check out the [[Pacman Rosetta]] article for a comparison to other popular package managers.
+
 
+
For repository selections and pacman options, edit {{ic|pacman.conf}}:
+
# nano /etc/pacman.conf
+
 
+
Most people will want to use {{ic|[core]}}, {{ic|[extra]}} and {{ic|[community]}}.
+
 
+
If you installed Arch Linux x86_64, it's recommended that you enable the {{ic|[multilib]}} repository, as well (to be able to run both 32 bit and 64 bit applications):
+
 
+
{{Note|When choosing repos, be sure to uncomment both the {{ic|[''repo_name'']}} header lines, as well as the lines below. Failure to do so will result in the selected repository being omitted! This is a very common error. A correct example for the multilib repository is found below.}}
+
 
+
[multilib]
+
SigLevel = PackageRequired
+
Include = /etc/pacman.d/mirrorlist
+
 
+
You will then need to update the package list by running {{ic|pacman}} with the {{ic|-Sy}} switch. Failing to do so will generate "warning: database file for 'multilib' does not exist" error when next using pacman.
+
 
+
See [[Official Repositories]] for more information, including details about the purpose of each repository.
+
 
+
For software unavailable directly through pacman, see [[Arch User Repository]].
+
 
+
=== Create an initial ramdisk environment ===
+
 
+
{{Tip|Most users can skip this step and use the defaults provided in {{ic|mkinitcpio.conf}}. The initramfs image (from the {{ic|/boot}} folder) has already been generated based on this file when the {{Pkg|linux}} package (the Linux kernel) was installed earlier with {{ic|pacstrap}}.}}
+
 
+
Here you need to set the right [[Mkinitcpio#HOOKS|hooks]] if the root is on a USB drive, if you use RAID, LVM, or if {{ic|/usr}} is on a separate partition.
+
 
+
Edit {{ic|/etc/mkinitcpio.conf}} as needed and re-generate the initramfs image with:
+
 
+
# mkinitcpio -p linux
+
 
+
{{Note|Arch VPS installations on QEMU (e.g. when using {{ic|virt-manager}}) may need {{ic|virtio}} modules in {{ic|mkinitcpio.conf}} to be able to boot.
+
 
+
{{hc|# nano /etc/mkinitcpio.conf|2=
+
MODULES="virtio virtio_blk virtio_pci virtio_net"}}}}
+
 
+
=== Set the root password and add a regular user ===
+
 
+
Set the root password with:
+
  
 
  # passwd
 
  # passwd
  
{{Warning|Linux is a multi-user operating system. You should not perform everyday tasks using the root account. It is considered a very poor practice and could be extremely dangerous. The root account should only be used for administrative tasks.}}
+
== Unmount the partitions and reboot ==
  
Then add a normal user account. For a more interactive way, you can use {{ic|adduser}}. However, below is the non-interactive way. The user ''archie'' is just an example.
+
Exit from the chroot environment by running {{ic|exit}} or pressing {{ic|Ctrl+D}}.  
  
# useradd -m -g users -G wheel -s /bin/bash ''archie''
+
Partitions will be unmounted automatically by ''systemd'' on shutdown. You may however unmount manually as a safety measure:
# passwd ''archie''
+
  
If you wish to start over, use {{ic|userdel}}. The {{ic|-r}} option will remove the user's home directory and its content, along with the user's settings (the so-called "dot" files).
+
# umount -R /mnt
  
# userdel -r ''archie''
+
If the partition is "busy", you can find the cause with [[fuser]]. Reboot the computer.
  
For more information, read [[Users and Groups]].
+
# reboot
  
=== Install and configure a bootloader ===
+
Remove the installation media, or you may boot back into it. You can log into your new installation as ''root'', using the password you specified with ''passwd''.
  
==== For BIOS motherboards ====
+
== Post-installation ==
  
For BIOS systems, there are three bootloaders - Syslinux, GRUB, and [[LILO]]. Choose the bootloader as per your convenience. Below only Syslinux and GRUB are explained.
+
Your new Arch Linux base system is now a functional GNU/Linux environment ready to be built into whatever you wish or require for your purposes. You are now ''strongly'' advised to read the [[General recommendations]] article, especially the first two sections. Its other sections provide links to post-installation tutorials like setting up a graphical user interface, sound or a touchpad.
 
+
* Syslinux is (currently) limited to loading only files from the partition where it was installed. Its configuration file is considered to be easier to understand. An example configuration can be found [https://bbs.archlinux.org/viewtopic.php?pid=1109328#p1109328 here].
+
 
+
* GRUB is more feature-rich and supports more complex scenarios. Its configuration file(s) is more similar to a scripting language, which may be difficult for beginners to manually write. It is recommended that they automatically generate one.
+
 
+
{{Note|Some BIOS systems may have issues with GPT. See http://mjg59.dreamwidth.org/8035.html and http://rodsbooks.com/gdisk/bios.html for more info and possible workarounds.}}
+
 
+
===== Syslinux =====
+
 
+
Install the {{Pkg|syslinux}} package and then use the {{ic|syslinux-install_update}} script to automatically ''install'' the files ({{ic|-i}}), mark the partition ''active'' by setting the boot flag ({{ic|-a}}), and install the ''MBR'' boot code ({{ic|-m}}):
+
 
+
{{Note|If you have partitioned the drive as GPT, install {{Pkg|gptfdisk}} package, as well ({{ic|pacman -S gptfdisk}}), because it contains {{ic|sgdisk}}, which will be used to set the GPT-specific boot flag.}}
+
 
+
# pacman -S syslinux
+
# syslinux-install_update -i -a -m
+
 
+
Configure {{ic|syslinux.cfg}} to point to the right root partition. This step is vital. If it points to the wrong partition, Arch Linux will not boot. Change {{ic|/dev/sda3}} to reflect your root partition ''(if you partitioned your drive as in [[#Prepare the storage drive|the example]], your root partition is sda1)''. Do the same for the fallback entry.
+
 
+
{{hc|# nano /boot/syslinux/syslinux.cfg|2=
+
...
+
LABEL arch
+
        ...
+
        APPEND root=/dev/sda3 ro
+
        ...}}
+
 
+
For more information on configuring and using Syslinux, see [[Syslinux]].
+
 
+
===== GRUB =====
+
 
+
Install the {{Pkg|grub-bios}} package and then run {{ic|grub-install}}:
+
 
+
{{Note|Change {{ic|/dev/sda}} to reflect the drive you installed Arch on. Do not append a partition number (do not use {{ic|sda''X''}}).}}
+
 
+
{{Note|For GPT-partitioned drives on BIOS motherboards, GRUB needs a 2 MiB "[[GRUB#GPT specific instructions|BIOS Boot Partition]]".}}
+
 
+
# pacman -S grub-bios
+
# grub-install --target=i386-pc --recheck /dev/sda
+
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
+
 
+
While using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:
+
 
+
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} ({{ic|pacman -S os-prober}}) before running the next command.}}
+
 
+
# grub-mkconfig -o /boot/grub/grub.cfg
+
 
+
For more information on configuring and using GRUB, see [[GRUB]].
+
 
+
==== For UEFI motherboards ====
+
 
+
For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or higher, FAT32, type {{ic|EF00}}) must be present and mounted on {{ic|/boot/efi}}. If you have followed this guide from the beginning, you've already done all of these.
+
 
+
While there are other [[UEFI Bootloaders|UEFI bootloaders]] available, using EFISTUB is recommended. Below are instructions for setting up EFISTUB and GRUB.
+
 
+
{{Note|Syslinux does not yet support UEFI.}}
+
 
+
===== EFISTUB =====
+
 
+
The Linux kernel can act as its own bootloader using EFISTUB. This is the UEFI boot method recommended by developers and simpler compared to {{ic|grub-efi-x86_64}}. The below steps set up rEFInd (a fork of rEFIt) to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. You can also use [[UEFI Bootloaders#Using gummiboot|gummiboot]] instead of rEFInd. Both rEFInd and gummiboot can detect Windows UEFI bootloader in case of dual-boot.
+
 
+
1. Boot in UEFI mode and load {{ic|efivars}} kernel module before chrooting:
+
 
+
# modprobe efivars      # before chrooting
+
 
+
2. Mount the UEFISYS partition at {{ic|/mnt/boot/efi}}, chroot and [[UEFI_Bootloaders#Setting_up_EFISTUB|copy the kernel and initramfs files]] as described below.
+
 
+
* Create {{ic|/boot/efi/EFI/arch/}} directory.
+
 
+
* Copy {{ic|/boot/vmlinuz-linux}} to {{ic|/boot/efi/EFI/arch/vmlinuz-arch.efi}}. The {{ic|.efi}} file extension is very important as some UEFI firmwares refuse to launch a file without this extension. '''Important:''' Remember that the file is called vmlinu'''z''', but not vmlinu'''x'''.
+
 
+
* Copy {{ic|/boot/initramfs-linux.img}} to {{ic|/boot/efi/EFI/arch/initramfs-arch.img}}.
+
 
+
* Copy {{ic|/boot/initramfs-linux-fallback.img}} to {{ic|/boot/efi/EFI/arch/initramfs-arch-fallback.img}}.
+
 
+
Every time the kernel and initramfs files are updated in {{ic|/boot}}, they need to be updated in {{ic|/boot/efi/EFI/arch}}. This can be automated either [[UEFI Bootloaders#Sync EFISTUB Kernel in UEFISYS partition using Systemd|using systemd]] or [[UEFI Bootloaders#Sync EFISTUB Kernel in UEFISYS partition using Incron|using incron]] (for non-systemd setups).
+
 
+
3. In this guide you set up a bootloader GUI called rEFInd. Alternative bootloaders can be found on the page [[UEFI Bootloaders#Booting EFISTUB]].
+
For the recommended rEFInd bootloader install the following packages:
+
# pacman -S refind-efi efibootmgr
+
 
+
4. Install rEFInd to the UEFISYS partition (summarized from [[UEFI Bootloaders#Using rEFInd]]):
+
 
+
# mkdir -p /boot/efi/EFI/refind
+
# cp /usr/lib/refind/refindx64.efi /boot/efi/EFI/refind/refindx64.efi
+
# cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf
+
# cp -r /usr/share/refind/icons /boot/efi/EFI/refind/icons
+
 
+
5. Create a {{ic|refind_linux.conf}} file with the kernel parameters to be used by rEFInd:
+
 
+
{{hc|# nano /boot/efi/EFI/arch/refind_linux.conf|2=
+
"Boot to X"          "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=graphical.target"
+
"Boot to console"    "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=multi-user.target"}}
+
 
+
{{Note|{{ic|refind_linux.conf}} is copied in the directory {{ic|/boot/efi/EFI/arch/}} where the initramfs and the kernel have been copied to in step 2. }}
+
 
+
6. Add rEFInd to UEFI boot menu using [[UEFI#efibootmgr|efibootmgr]].
+
 
+
{{Warning|Using {{ic|efibootmgr}} on Apple Macs may brick the firmware and may need reflash of the motherboard ROM. For Macs, use {{AUR|mactel-boot}}, or "bless" from within Mac OS X.}}
+
 
+
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "rEFInd" -l '\EFI\refind\refindx64.efi'
+
 
+
{{Note|In the above command, X and Y denote the drive and partition of the UEFISYS partition. For example, in {{ic|/dev/sdc5}}, X is "c" and Y is "5".}}
+
 
+
7. (Optional) As a fallback, in case {{ic|efibootmgr}} created boot entry does not work, copy {{ic|refindx64.efi}} to {{ic|/boot/efi/EFI/boot/bootx64.efi}} as follows:
+
 
+
# cp -r /boot/efi/EFI/refind/* /boot/efi/EFI/boot/
+
# mv /boot/efi/EFI/boot/refindx64.efi /boot/efi/EFI/boot/bootx64.efi
+
 
+
===== GRUB =====
+
 
+
{{Note|In case you have a system with 32-bit EFI, like pre-2008 Macs, install {{ic|grub-efi-i386}} instead, and use {{ic|1=--target=i386-efi}}.}}
+
 
+
# pacman -S grub-efi-x86_64 efibootmgr
+
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck
+
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
+
 
+
The next command creates a menu entry for GRUB in the UEFI boot menu. However, as of {{Pkg|grub-efi-x86_64}} version 2.00, {{ic|grub-install}} tries to create a menu entry, so running {{ic|efibootmgr}} may not be necessary. See [[UEFI#efibootmgr]] for more info.
+
 
+
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "Arch Linux (GRUB)" -l '\EFI\arch_grub\grubx64.efi'
+
 
+
Next, while using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:
+
 
+
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} ({{ic|pacman -S os-prober}}) before running the next command.}}
+
 
+
# grub-mkconfig -o /boot/grub/grub.cfg
+
 
+
For more information on configuring and using GRUB, see [[GRUB]].
+
 
+
=== Unmount the partitions and reboot ===
+
 
+
Exit from the chroot environment:
+
 
+
# exit
+
 
+
Since the partitions are mounted under {{ic|/mnt}}, we use the following command to unmount them:
+
 
+
# umount /mnt/{boot,home,}
+
 
+
Reboot the computer:
+
 
+
# reboot
+
  
{{Tip|Be sure to remove the installation media, otherwise you will boot back into it.}}<noinclude>
+
For a list of applications that may be of interest, see [[List of applications]].
{{Beginners' Guide navigation}}</noinclude>
+

Latest revision as of 20:09, 25 May 2016

This document will guide you through the process of installing Arch Linux using the Arch Install Scripts. Before installing, you are advised to skim over the FAQ.

The community-maintained ArchWiki is the primary resource that should be consulted if issues arise. The IRC channel (irc://irc.freenode.net/#archlinux) and the forums are also excellent resources if an answer cannot be found elsewhere. In accordance with the Arch Way, you are encouraged to type man command to read the man page of any command you are unfamiliar with.

Preparation

Arch Linux should run on any i686 compatible machine with a minimum of 256 MB RAM. A basic installation with all packages from the base group should take less than 800 MB of disk space.

See Category:Getting and installing Arch for instructions on downloading the installation medium, and methods for booting it to the target machine(s). This guide assumes you use the latest available version.

Boot the installation medium

Point the current boot device to the drive containing the Arch installation media. This is typically achieved by pressing a key during the POST phase, as indicated on the splash screen. Refer to your motherboard's manual for details.

When the Arch menu appears, select Boot Arch Linux and press Enter to enter the installation environment. See README.bootparams for a list of boot parameters.

You will be logged in as the root user and presented with a Zsh shell prompt. Zsh provides advanced tab completion and other features as part of the grml config. For modifying or creating configuration files, typically in /etc, nano and vim are suggested.

UEFI mode

In case you have a UEFI motherboard with UEFI mode enabled, the CD/USB will automatically launch Arch Linux via systemd-boot.

To verify you are booted in UEFI mode, check that the following directory is populated:

# ls /sys/firmware/efi/efivars

See UEFI#UEFI Variables for details.

Set the keyboard layout

The default console keymap is set to us. Available choices can be listed with ls /usr/share/kbd/keymaps/**/*.map.gz.

Note: localectl list-keymaps does not work due to bug FS#46725.

For example, to change the layout to de-latin1, run:

# loadkeys de-latin1

If certain characters appear as white squares or other symbols, change the console font. For example:

# setfont lat9w-16

Connect to the Internet

Wired

The dhcpcd daemon is enabled on boot for wired devices, and will attempt to start a connection. To access captive portal login forms, use the ELinks browser.

Verify a connection was established, for example with ping. If none is available, proceed to configure the network; the examples below use netctl to this purpose. To prevent conflicts, stop the dhcpcd service (replacing enp0s25 with the correct wired interface):

# systemctl stop dhcpcd@enp0s25.service

Interfaces can be listed using ip link, or iw dev for wireless devices. They are prefixed with en (ethernet), wl (WLAN), or ww (WWAN).

Wireless

List available networks, and make a connection for a specified interface:

# wifi-menu -o wlp2s0

The resulting configuration file is stored in /etc/netctl. For networks which require both a username and password, see WPA2 Enterprise#netctl.

Other

Several example profiles, such as for configuring a static IP address, are available. Copy the required one to /etc/netctl, for example ethernet-static:

# cp /etc/netctl/examples/ethernet-static /etc/netctl

Adjust the copy as needed, and enable it:

# netctl start ethernet-static

Update the system clock

Use systemd-timesyncd to ensure that your system clock is accurate. To start it:

# timedatectl set-ntp true

To check the service status, use timedatectl status.

Prepare the storage devices

Warning:
  • In general, partitioning or formatting will make existing data inaccessible and subject to being overwritten, i.e. destroyed, by subsequent operations. For this reason, all data that needs to be preserved must be backed up before proceeding.
  • If dual-booting with an existing installation of Windows on a UEFI/GPT system, avoid reformatting the UEFI partition, as this includes the Windows .efi file required to boot it. Furthermore, Arch must follow the same firmware boot mode and partitioning combination as Windows. See Dual boot with Windows#Important information.

In this step, the storage devices that will be used by the new system will be prepared. Read Partitioning for a more general overview.

Users intending to create stacked block devices for LVM, disk encryption or RAID, should keep those instructions in mind when preparing the partitions. If intending to install to a USB flash key, see Installing Arch Linux on a USB key.

Identify the devices

The first step is to identify the devices where the new system will be installed. The following command will show all the available devices:

# lsblk

This will list all devices connected to your system along with their partition schemes, including that used to host and boot live Arch installation media (e.g. a USB drive). Not all devices listed will therefore be viable or appropriate mediums for installation. Results ending in rom, loop or airoot can be ignored.

Devices (e.g. hard disks) will be listed as sdx, where x is a lower-case letter starting from a for the first device (sda), b for the second device (sdb), and so on. Existing partitions on those devices will be listed as sdxY, where Y is a number starting from 1 for the first partition, 2 for the second, and so on. In the example below, only one device is available (sda), and that device has only one partition (sda1):

NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0    80G  0 disk
└─sda1            8:1    0    80G  0 part

The sdxY convention will be used in the examples provided below for partition tables, partitions, and file systems. As they are just examples, it is important to ensure that any necessary changes to device names, partition numbers, and/or partition sizes (etc.) are made. Do not just blindly copy and paste the commands.

If the existing partition scheme does not need to be changed, skip to #Format the file systems and enable swap, otherwise continue reading the following section.

Partition table types

If you are installing alongside an existing installation (i.e. dual-booting), a partition table will already be in use. If the devices are not partitioned, or the current partitions table or scheme needs to be changed, you will first have to determine the partition tables (one for each device) in use or to be used.

There are two types of partition table:

Any existing partition table can be identified with the following command for each device:

# parted /dev/sdx print

Partitioning tools

Warning: Using a partitioning tool that is incompatible with your partition table type will likely result in the destruction of that table, along with any existing partitions/data.

For each device to be partitioned, a proper tool must be chosen according to the partition table to be used. Several partitioning tools are provided by the Arch installation medium, including:

  • parted: GPT and MBR
  • fdisk, cfdisk, sfdisk: GPT and MBR
  • gdisk, cgdisk, sgdisk: GPT

Devices may also be partitioned before booting the installation media, for example through tools such as GParted (also provided as a live CD).

Using parted in interactive mode

All the examples provided below make use of parted, as it can be used for both UEFI/GPT and BIOS/MBR. It will be launched in interactive mode, which simplifies the partitioning process and reduces unnecessary repetition by automatically applying all partitioning commands to the specified device.

In order to start operating on a device, execute:

# parted /dev/sdx

You will notice that the command-line prompt changes from a hash (#) to (parted): this also means that the new prompt is not a command to be manually entered when running the commands in the examples.

To see a list of the available commands, enter:

(parted) help

When finished, or if wishing to implement a partition table or scheme for another device, exit from parted with:

(parted) quit

After exiting, the command-line prompt will change back to #.

Create new partition table

You need to (re)create the partition table of a device when it has never been partitioned before, or when you want to change the type of its partition table. Recreating the partition table of a device is also useful when the partition scheme needs to be restructured from scratch.

Open each device whose partition table must be (re)created with:

# parted /dev/sdx

To then create a new GPT partition table for UEFI systems, use the following command:

(parted) mklabel gpt

To create a new MBR/msdos partition table for BIOS systems instead, use:

(parted) mklabel msdos

Partition schemes

You can decide the number and size of the partitions the devices should be split into, and which directories will be used to mount the partitions in the installed system (also known as mount points). The mapping from partitions to directories is the partition scheme, which must comply with the following requirements:

  • At least a partition for the / (root) directory must be created.
  • When using a UEFI motherboard, one EFI System Partition must be created.

In the examples below it is assumed that a new and contiguous partitioning scheme is applied to a single device. Some optional partitions will also be created for the /boot and /home directories which otherwise would simply be contained in the / partition. See the Arch filesystem hierarchy for an explanation of the purpose of the various directories. Also the creation of an optional partiton for swap space will be illustrated.

If not already open in a parted interactive session, open each device to be partitioned with:

# parted /dev/sdx

The following command will be used to create partitions:

(parted) mkpart part-type fs-type start end
  • part-type is one of primary, extended or logical, and is meaningful only for MBR partition tables.
  • fs-type is an identifier chosen among those listed by entering help mkpart as the closest match to the file system that you will use in #Format the file systems and enable swap. The mkpart command does not actually create the file system: the fs-type parameter will simply be used by parted to set a 1-byte code that is used by boot loaders to "preview" what kind of data is found in the partition, and act accordingly if necessary. See also Wikipedia:Disk partitioning#PC partition types.
Tip: Most Linux native file systems map to the same partition code (0x83), so it is perfectly safe to e.g. use ext2 for an ext4-formatted partition.
  • start is the beginning of the partition from the start of the device. It consists of a number followed by a unit, for example 1M means start at 1MiB.
  • end is the end of the partition from the start of the device (not from the start value). It has the same syntax as start, for example 100% means end at the end of the device (use all the remaining space).
Warning: It is important that the partitions do not overlap each other: if you do not want to leave unused space in the device, make sure that each partition starts where the previous one ends.
Note: parted may issue a warning like:
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel?
In this case, read Partitioning#Partition alignment and follow GNU Parted#Alignment to fix it.

The following command will be used to flag the partition that contains the /boot directory as bootable:

(parted) set partition boot on
  • partition is the number of the partition to be flagged (see the output of the print command).

UEFI/GPT examples

In every instance, a special bootable EFI System Partition is required.

If creating a new EFI System Partition, use the following commands (a size of 512MiB is suggested):

(parted) mkpart ESP fat32 1MiB 513MiB
(parted) set 1 boot on

The remaining partition scheme is entirely up to you. For one other partition using 100% of remaining space:

(parted) mkpart primary ext4 513MiB 100%

For separate / (20GiB) and /home (all remaining space) partitions:

(parted) mkpart primary ext4 513MiB 20.5GiB
(parted) mkpart primary ext4 20.5GiB 100%

And for separate / (20GiB), swap (4GiB), and /home (all remaining space) partitions:

(parted) mkpart primary ext4 513MiB 20.5GiB
(parted) mkpart primary linux-swap 20.5GiB 24.5GiB
(parted) mkpart primary ext4 24.5GiB 100%

BIOS/MBR examples

For a minimum single primary partition using all available disk space, the following command would be used:

(parted) mkpart primary ext4 1MiB 100%
(parted) set 1 boot on

In the following instance, a 20GiB / partition will be created, followed by a /home partition using all the remaining space:

(parted) mkpart primary ext4 1MiB 20GiB
(parted) set 1 boot on
(parted) mkpart primary ext4 20GiB 100%

In the final example below, separate /boot (100MiB), / (20GiB), swap (4GiB), and /home (all remaining space) partitions will be created:

(parted) mkpart primary ext4 1MiB 100MiB
(parted) set 1 boot on
(parted) mkpart primary ext4 100MiB 20GiB
(parted) mkpart primary linux-swap 20GiB 24GiB
(parted) mkpart primary ext4 24GiB 100%

Format the file systems and enable swap

Once the partitions have been created, each must be formatted with an appropriate file system, except for swap partitions. All available partitions on the intended installation device can be listed with the following command:

# lsblk /dev/sdx

With the exceptions noted below, it is recommended to use the ext4 file system:

# mkfs.ext4 /dev/sdxY

If a swap partition has been created, it must be set up and activated with:

# mkswap /dev/sdxY
# swapon /dev/sdxY

Mount the root partition to the /mnt directory of the live system:

# mount /dev/sdxY /mnt

Remaining partitions (except swap) may be mounted in any order, after creating the respective mount points. For example, when using a /boot partition:

# mkdir -p /mnt/boot
# mount /dev/sdxZ /mnt/boot

If a new UEFI system partition has been created on a UEFI/GPT system, it must be formatted with a fat32 file system:

# mkfs.fat -F32 /dev/sdxY

/mnt/boot is also recommended for mounting the (formatted or already existing) EFI System Partition on a UEFI/GPT system. See EFISTUB and related articles for alternatives.

Installation

Select the mirrors

Packages to be installed must be downloaded from mirror servers, which are defined in /etc/pacman.d/mirrorlist. On the live system, all mirrors are enabled, and sorted by their synchronization status and speed at the time the installation image was created.

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

pacstrap will also install a copy of this file to the new system, so it is worth getting right.

Install the base packages

The pacstrap script installs the base system. To build packages from the AUR or with ABS, the base-devel group is also required.

Not all tools from the live installation (see packages.both) are part of the base group. Packages can later be installed with pacman, or by appending their names to the pacstrap command.

# pacstrap -i /mnt base base-devel

The -i switch ensures prompting before package installation.

Configuration

fstab

Generate an fstab file. The -U option indicates UUIDs: see Persistent block device naming. Labels can be used instead through the -L option.

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

Check the resulting file in /mnt/etc/fstab afterwards, and edit it in case of errors.

Change root

Copy netctl profiles in /etc/netctl to the new system in /mnt (when applicable), then chroot to it:

# arch-chroot /mnt /bin/bash

Locale

The Locale defines which language the system uses, and other regional considerations such as currency denomination, numerology, and character sets.

Possible values are listed in /etc/locale.gen. Uncomment en_US.UTF-8 UTF-8, as well as other needed localisations. Save the file, and generate the new locales:

# locale-gen

Create /etc/locale.conf, where LANG refers to the first column of an uncommented entry in /etc/locale.gen:

/etc/locale.conf
LANG=en_US.UTF-8

If you set the keyboard layout, make the changes persistent in /etc/vconsole.conf. For example, if de-latin1 was set with loadkeys, and lat9w-16 with setfont, assign the KEYMAP and FONT variables accordingly:

/etc/vconsole.conf
KEYMAP=de-latin1
FONT=lat9w-16

Time

Select a time zone:

# tzselect

Create the symbolic link /etc/localtime, where Zone/Subzone is the TZ value from tzselect:

# ln -s /usr/share/zoneinfo/Zone/SubZone /etc/localtime

It is recommended to adjust the time skew, and set the time standard to UTC:

# hwclock --systohc --utc

If other operating systems are installed on the machine, they must be configured accordingly. See Time for details.

Initramfs

As mkinitcpio was run on installation of linux with pacstrap, most users can use the defaults provided in mkinitcpio.conf.

For special configurations, set the correct hooks in /etc/mkinitcpio.conf and re-generate the initramfs image:

# mkinitcpio -p linux

Install a boot loader

See Boot loaders for available choices and configurations. If you have an Intel CPU, install the intel-ucode package, and enable microcode updates.

UEFI/GPT

Here, the installation drive is assumed to be GPT-partioned, and have the EFI System Partition (gdisk type EF00, formatted with FAT32) mounted at /boot.

Install systemd-boot to the EFI system partition:

# bootctl install

When successful, create a boot entry as described in systemd-boot#Configuration (replacing $esp with /boot), or adapt the examples in /usr/share/systemd/bootctl/.

BIOS/MBR

Install the grub package. To search for other operating systems, also install os-prober:

# pacman -S grub os-prober

Install the bootloader to the drive Arch was installed to:

# grub-install --target=i386-pc /dev/sda

Generate grub.cfg:

# grub-mkconfig -o /boot/grub/grub.cfg

See GRUB for more information.

Configure the network

The procedure is similar to #Connect to the Internet, except made persistent for subsequent boots. Select one daemon to handle the network.

Hostname

Set the hostname to your liking by adding myhostname to the following file, where myhostname is the hostname you wish to set:

/etc/hostname
myhostname

It is recommended to append the same hostname to localhost entries in /etc/hosts. See Network configuration#Set the hostname for details.

Wired

When only requiring a single wired connection, enable the dhcpcd service:

# systemctl enable dhcpcd@interface.service

Where interface is an ethernet device name.

See Network configuration#Configure the IP address for other available methods.

Wireless

Install iw, wpa_supplicant, and (for wifi-menu) dialog:

# pacman -S iw wpa_supplicant dialog

Additional firmware packages may also be required.

If you used wifi-menu priorly, repeat the steps after finishing the rest of this installation and rebooting, to prevent conflicts with the existing processes.

See Netctl and Wireless#Wireless management for more information.

Root password

Set the root password with:

# passwd

Unmount the partitions and reboot

Exit from the chroot environment by running exit or pressing Ctrl+D.

Partitions will be unmounted automatically by systemd on shutdown. You may however unmount manually as a safety measure:

# umount -R /mnt

If the partition is "busy", you can find the cause with fuser. Reboot the computer.

# reboot

Remove the installation media, or you may boot back into it. You can log into your new installation as root, using the password you specified with passwd.

Post-installation

Your new Arch Linux base system is now a functional GNU/Linux environment ready to be built into whatever you wish or require for your purposes. You are now strongly advised to read the General recommendations article, especially the first two sections. Its other sections provide links to post-installation tutorials like setting up a graphical user interface, sound or a touchpad.

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