{{Warning|udev no longer assigns network interface names according to the wlanX and ethX naming scheme. If you're coming from a different distribution or are reinstalling Arch and not aware of the new interface naming style, please do not assume that your wireless interface is named wlan0, or that your wired interface is named eth0. You can use the command {{ic|ip addr show}} to discover the names of your interfaces.}}

+

{{Warning|udev no longer assigns network interface names according to the wlanX and ethX naming scheme. If you are coming from a different distribution or are reinstalling Arch and not aware of the new interface naming style, please do not assume that your wireless interface is named wlan0, or that your wired interface is named eth0. You can use the command {{ic|ip addr show}} to discover the names of your interfaces.}}

From systemd-197's release and onward, udev now assigns predictable, stable network interface names that deviate from the legacy incremental naming scheme (wlan0, wlan1, etc.). These interface names are guaranteed to be persistent across reboots, which solves the problem of the lack of predictability of network interface name assignment. For more information about why this was necessary, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .

From systemd-197's release and onward, udev now assigns predictable, stable network interface names that deviate from the legacy incremental naming scheme (wlan0, wlan1, etc.). These interface names are guaranteed to be persistent across reboots, which solves the problem of the lack of predictability of network interface name assignment. For more information about why this was necessary, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .

Line 90:

Line 90:

link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff}}

link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff}}

−

In this example, the Ethernet interface is {{ic|enp2s0f0}}. If you're unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be "lo" or start with the letter "w". You can also use {{ic|iwconfig}} and see which interfaces are not wireless:

+

In this example, the Ethernet interface is {{ic|enp2s0f0}}. If you are unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be "lo" or start with the letter "w". You can also use {{ic|iwconfig}} and see which interfaces are not wireless:

{{hc|# iwconfig|2=

{{hc|# iwconfig|2=

Line 112:

Line 112:

* Gateway's IP address.

* Gateway's IP address.

* Name servers' (DNS) IP addresses.

* Name servers' (DNS) IP addresses.

−

* Domain name (unless you're on a local LAN, in which case you can make it up).

+

* Domain name (unless you are on a local LAN, in which case you can make it up).

Activate the connected Ethernet interface (e.g. {{ic|enp2s0f0}}):

Activate the connected Ethernet interface (e.g. {{ic|enp2s0f0}}):

Line 165:

Line 165:

lo no wireless extensions.}}

lo no wireless extensions.}}

−

In this example, {{ic|wlp3s0}} is the available wireless interface. If you're unsure, your wireless interface is likely to start with the letter "w", and unlikely to be "lo" or start with the letter "e".

+

In this example, {{ic|wlp3s0}} is the available wireless interface. If you are unsure, your wireless interface is likely to start with the letter "w", and unlikely to be "lo" or start with the letter "e".

{{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.}}

{{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.}}

Line 189:

Line 189:

{{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.}}

{{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.}}

−

Next, use {{Pkg|netcfg}}'s {{ic|wifi-menu}} to connect to a network:

+

Next, use {{Pkg|netctl}}'s {{ic|wifi-menu}} to connect to a network:

# wifi-menu wlp3s0

# wifi-menu wlp3s0

Line 195:

Line 195:

You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.

You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.

−

==== xDSL (PPPoE), analog modem or ISDN ====

+

==== Analog modem, ISDN or PPoE DSL ====

−

If you have a router in bridge mode, run:

+

For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].

−

−

# pppoe-setup

−

−

* Type in the username that the ISP provided you with.

−

* 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:

−

−

# pppoe-start

−

−

You may also need to adjust your {{ic|resolv.conf}}:

−

−

# echo nameserver 8.8.8.8 > /etc/resolv.conf

−

−

If you have a dial-up or ISDN connection, see [[Direct Modem Connection]].

==== Behind a proxy server ====

==== Behind a proxy server ====

Line 229:

Line 209:

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.

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.

−

The recommendation for a system that will boot via UEFI rather than MBR legacy boot is to format the drive using a GPT partition table. This means that if the drive was previously already partitioned with an MBR (MSDOS) partition table it will now have a new partition table created which will destroy all other data on the drive. Once the new partition table has been created on a drive, only then can individual partitions be created with any chosen format type. When using Gparted, selecting the option to create a new partition table gives an "msdos" partition table by default. If you are intending to follow the advice to create a GPT partition table then you need to choose "Advanced" and then select "gpt" from the drop-down menu. This can't be done if you have a pre-existing Windows installation on the drive which you wish not to destroy. It is therefore extremely important to not change the partition table to GPT if you intend on having a dual boot system. Leave the Windows install untouched and try to get the Linux install working with UEFI on a drive that contains an MBR (legacy) partition table.

+

The recommendation for a system that will boot via UEFI rather than MBR legacy boot is to format the drive using a GPT partition table. This means that if the drive was previously already partitioned with an MBR (MSDOS) partition table it will now have a new partition table created which will destroy all other data on the drive. Once the new partition table has been created on a drive, only then can individual partitions be created with any chosen format type. When using Gparted, selecting the option to create a new partition table gives an "msdos" partition table by default. If you are intending to follow the advice to create a GPT partition table then you need to choose "Advanced" and then select "gpt" from the drop-down menu. This cannot be done if you have a pre-existing Windows installation on the drive which you wish not to destroy. It is therefore extremely important to not change the partition table to GPT if you intend on having a dual boot system. Leave the Windows install untouched and try to get the Linux install working with UEFI on a drive that contains an MBR (legacy) partition table.

In addition, some newer computers come pre-installed with Windows 8 which will be using Secure Boot. Arch Linux currently does not support Secure Boot, but some Windows 8 installations have been seen not to boot if Secure Boot is turned off in the BIOS. In some cases it is necessary to turn off both Secure Boot as well as Fastboot in the BIOS options in order to allow Windows 8 to boot without Secure Boot. However there are potential security risks in turning off Secure Boot for booting up Windows 8. Therefore, it may be a better option to keep the Windows 8 install intact and have an independent hard drive for the Linux install - which can then be partitioned from scratch using a GPT partition table. Once that is done, creating several ext4/FAT32/swap partitions on the second drive may be a better way forward if the computer has two drives available. This is often not easy or possible on a small laptop. Currently, Secure Boot is still not in a fully stable state for reliable operation, even for Linux distributions that support it.

In addition, some newer computers come pre-installed with Windows 8 which will be using Secure Boot. Arch Linux currently does not support Secure Boot, but some Windows 8 installations have been seen not to boot if Secure Boot is turned off in the BIOS. In some cases it is necessary to turn off both Secure Boot as well as Fastboot in the BIOS options in order to allow Windows 8 to boot without Secure Boot. However there are potential security risks in turning off Secure Boot for booting up Windows 8. Therefore, it may be a better option to keep the Windows 8 install intact and have an independent hard drive for the Linux install - which can then be partitioned from scratch using a GPT partition table. Once that is done, creating several ext4/FAT32/swap partitions on the second drive may be a better way forward if the computer has two drives available. This is often not easy or possible on a small laptop. Currently, Secure Boot is still not in a fully stable state for reliable operation, even for Linux distributions that support it.

{{Tip|Use the {{ic|lsblk}} command to list the hard disks attached to your system, along with the sizes of their existing partitions. This will help you to be confident you are partitioning the right disk.}}

{{Box BLUE|Notes regarding [[UEFI]] boot:|

{{Box BLUE|Notes regarding [[UEFI]] boot:|

Line 249:

Line 231:

{{Box BLUE|Notes regarding [[GPT]] partitioning:|

{{Box BLUE|Notes regarding [[GPT]] partitioning:|

* 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 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 an extra [[GRUB2#GUID Partition Table (GPT) specific instructions|BIOS Boot Partition]]. Syslinux doesn't need one.

+

* 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 an extra [[GRUB#GUID Partition Table (GPT) specific instructions|BIOS Boot Partition]]. Syslinux does not 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.}}

* 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.}}

Line 284:

Line 266:

|}

|}

−

If you chose MBR, here's how it should look like:

+

If you chose MBR, here is what it should look like:

Name Flags Part Type FS Type [Label] Size (MB)

Name Flags Part Type FS Type [Label] Size (MB)

Line 291:

Line 273:

sda2 Primary Linux 133000*

sda2 Primary Linux 133000*

−

If you chose GPT, here's how it should look like:

+

If you chose GPT, here is what it should look like:

Part. # Size Partition Type Partition Name

Part. # Size Partition Type Partition Name

Line 307:

Line 289:

Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:

Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:

−

{{Warning|Double check and triple check that it's actually {{ic|/dev/sda1}} and {{ic|/dev/sda2}} that you want to format.}}

+

{{Warning|Double check and triple check that it is actually {{ic|/dev/sda1}} and {{ic|/dev/sda2}} that you want to format. You can use {{ic|lsblk}} to help with this.}}

# mkfs.ext4 /dev/sda1

# mkfs.ext4 /dev/sda1

# mkfs.ext4 /dev/sda2

# mkfs.ext4 /dev/sda2

−

If you have made a partition dedicated to swap (code 82), don't forget to format and activate it with:

+

If you have made a partition dedicated to swap (code 82), do not forget to format and activate it with:

# mkswap /dev/sda''X''

# mkswap /dev/sda''X''

Line 343:

Line 325:

=== Select a mirror ===

=== Select a mirror ===

−

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.

+

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 is worth getting it right.

{{hc|# nano /etc/pacman.d/mirrorlist|

{{hc|# nano /etc/pacman.d/mirrorlist|

Line 360:

Line 342:

* {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.

* {{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 you want, you can make it the ''only'' mirror available by getting rid of everything else (using {{Keypress|Ctrl+K}}), but it is usually a good idea to have a few more, in case the first one goes offline.

{{Tip|

{{Tip|

Line 368:

Line 350:

{{Note|

{{Note|

* 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.

* 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.

+

* If you are 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.}}

* 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.}}

Line 427:

Line 409:

This will run on every '''glibc''' upgrade, generating all the locales specified in {{ic|/etc/locale.gen}}.

This will run on every '''glibc''' upgrade, generating all the locales specified 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.

+

* The {{ic|locale.conf}} file does not exist by default. Setting only {{ic|LANG}} should be enough. It will act as the default value for all other variables.

# echo LANG=en_US.UTF-8 > /etc/locale.conf

# echo LANG=en_US.UTF-8 > /etc/locale.conf

Line 455:

Line 437:

* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.

* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.

−

* {{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".

+

* {{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 is 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".

* 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''.

* 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''.

−

* 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.

+

* 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 do not 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.

==== Kernel modules ====

==== Kernel modules ====

Line 538:

Line 520:

==== Wired ====

==== Wired ====

−

; Dynamic IP

+

{{Warning|A bug has been noted in the install ISO, in which the name your interface has during installation differs from the one it will have upon reboot. See {{Bug|33923}} for more details.<br/>

+

+

Use the command {{ic|ip link}} (shows interface names) after rebooting into your installed system to find out if you are affected by this. If so, you will have to redo the configuration described below with the correct interface name.}}

−

{{Warning|A bug has been noted in the install ISO, in which the name your interface has during installation differs from the one it will have upon reboot. See [https://bugs.archlinux.org/task/33923 Bug #33923] for more details.<br/>

+

===== Dynamic IP =====

−

Use the command {{ic|ip link}} (shows interface names) after rebooting into your installed system to find out if you are affected by this. If so, you will have to redo the configuration described below with the correct interface name.}}

+

; Using dhcpcd

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. Here, {{ic|''interface_name''}} is your wired interface:

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. Here, {{ic|''interface_name''}} is your wired interface:

Line 548:

Line 532:

# systemctl enable dhcpcd@''interface_name''.service

# systemctl enable dhcpcd@''interface_name''.service

−

And that's it.

+

; Using netctl

−

Move on to the next step: [[Beginners%27_Guide/Installation#Create_an_initial_ramdisk_environment|Create an initial ramdisk environment]].

+

Copy a sample profile from {{ic|/etc/netctl/examples}} to {{ic|/etc/netctl/}}:

−

Alternatively, you can use {{Pkg|netcfg}}'s {{ic|net-auto-wired}}, which gracefully handles dynamic connections to new networks:

+

# cd /etc/netctl

+

# cp examples/ethernet-dhcp .

−

Install {{Pkg|ifplugd}}, which is required for {{ic|net-auto-wired}}:

+

Edit the profile as needed (modify {{ic|Interface}}):

−

# pacman -S ifplugd

+

# nano ethernet-dhcp

+

+

Enable the {{ic|ethernet-dhcp}} profile:

−

Edit {{ic|/etc/conf.d/netcfg}} and modify the network interface name, most likely it is not eth0. You can find out more about the naming in the warning above.

+

# netctl enable ethernet-dhcp

−

{{hc|# nano /etc/conf.d/netcfg|2=

+

; Using netctl-ifplugd

−

WIRED_INTERFACE="''interface_name''"}}

−

Copy a sample profile from {{ic|/etc/network.d/examples}} to {{ic|/etc/network.d}}:

+

Alternatively, you can use {{Pkg|netctl}}'s {{ic|netctl-ifplugd}}, which gracefully handles dynamic connections to new networks:

−

# cd /etc/network.d

+

Install {{Pkg|ifplugd}}, which is required for {{ic|netctl-ifplugd}}:

−

# cp examples/ethernet-dhcp .

−

Edit the profile as needed (modify {{ic|INTERFACE}}):

+

# pacman -S ifplugd

−

# nano ethernet-dhcp

+

Then enable for interface that you want:

−

Enable the {{ic|net-auto-wired}} service:

+

# systemctl enable netctl-ifplugd@<interface>.service

−

# systemctl enable net-auto-wired.service

+

===== Static IP =====

−

; Static IP

+

; Using netctl

−

Copy a sample profile from {{ic|/etc/network.d/examples}} to {{ic|/etc/network.d}}:

+

Copy a sample profile from {{ic|/etc/netctl/examples}} to {{ic|/etc/netctl/}}:

Edit {{ic|/etc/conf.d/netcfg}} and add the new network profile to the {{ic|NETWORKS}} array:

+

Then enable above created profile:

−

{{hc|nano /etc/conf.d/netcfg|2=

+

# netctl enable ethernet-static

−

NETWORKS=(ethernet-static)}}

−

Enable the {{ic|netcfg}} service:

+

==== Wireless ====

−

−

# systemctl enable netcfg.service

−

==== Wireless ====

+

{{Out of date|netcfg is no longer in the official repositories. The following section needs to be changed to use {{pkg|netctl}} instead.}}

You will need to install additional programs to be able to configure and manage wireless network profiles for [[netcfg]].

You will need to install additional programs to be able to configure and manage wireless network profiles for [[netcfg]].

Line 616:

Line 598:

# wifi-menu ''interface_name''

# wifi-menu ''interface_name''

−

{{Warning|If you're using {{ic|wifi-menu}}, this must be done *after* your reboot when you're no longer chrooted. The process spawned by this command will conflict with the one you have running outside of the chroot. Alternatively, you could just configure a network profile manually using the templates previously mentioned so that you don't have to worry about using {{ic|wifi-menu}} at all.}}

+

{{Warning|If you are using {{ic|wifi-menu}}, this must be done *after* your reboot when you are no longer chrooted. The process spawned by this command will conflict with the one you have running outside of the chroot. Alternatively, you could just configure a network profile manually using the templates previously mentioned so that you do not have to worry about using {{ic|wifi-menu}} at all.}}

* Enable the {{ic|net-auto-wireless}} service, which will connect to known networks and gracefully handle roaming and disconnects:

* Enable the {{ic|net-auto-wireless}} service, which will connect to known networks and gracefully handle roaming and disconnects:

Line 635:

Line 617:

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.

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 ====

+

==== Analog modem, ISDN or PPoE DSL ====

For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].

For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].

Line 698:

Line 680:

{{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|Change {{ic|/dev/sda}} to reflect the drive you installed Arch on. Do not append a partition number (do not use {{ic|sda''X''}}).}}

While using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:

+

While using a manually created {{ic|grub.cfg}} is absolutely fine, it is 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.}}

{{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.}}

Line 710:

Line 692:

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

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

−

For more information on configuring and using GRUB, see [[GRUB2]].

+

For more information on configuring and using GRUB, see [[GRUB]].

==== For UEFI motherboards ====

==== For UEFI motherboards ====

−

For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or larger, type {{ic|EF00}}, formatted with FAT32) 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.

+

For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or larger, type {{ic|EF00}}, formatted with FAT32) must be present and mounted on {{ic|/boot/efi}}. If you have followed this guide from the beginning, you have 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 (of course you choose only one of them).

While there are other [[UEFI Bootloaders|UEFI bootloaders]] available, using EFISTUB is recommended. Below are instructions for setting up EFISTUB and GRUB (of course you choose only one of them).

Line 724:

Line 706:

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 steps below set up rEFInd to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. Alternative EFISTUB boot managers can be found on the page [[UEFI Bootloaders#Booting EFISTUB]]. Both rEFInd and [[gummiboot]] can detect Windows UEFI bootloaders in case of dual-boot.

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 steps below set up rEFInd to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. Alternative EFISTUB boot managers can be found on the page [[UEFI Bootloaders#Booting EFISTUB]]. Both rEFInd and [[gummiboot]] can detect Windows UEFI bootloaders in case of dual-boot.

−

1a. Before chrooting, load the {{ic|efivars}} kernel module:

+

1. Mount the UEFI System Partition on {{ic|/mnt/boot/efi}} and chroot back into {{ic|/mnt}}.

−

−

# modprobe efivars # before chrooting

−

−

1b. Mount the UEFI System Partition on {{ic|/mnt/boot/efi}} and chroot back into {{ic|/mnt}}.

2. [[UEFI Bootloaders#Setting up EFISTUB|Copy the kernel and initramfs files]] to {{ic|/mnt/boot/efi}}:

2. [[UEFI Bootloaders#Setting up EFISTUB|Copy the kernel and initramfs files]] to {{ic|/mnt/boot/efi}}:

Line 763:

Line 741:

{{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 OS X.}}

{{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 OS X.}}

{{Note|On some systems, the above command will not work properly. It will execute without any visible error, but the UEFI boot menu will not have been correctly updated with a new entry. To determine whether the command executed properly, run {{ic|efibootmgr}} without any arguments and see if a new entry has appeared in the list displayed. If there is no new entry, then it will not be possible to enter rEFInd upon reboot, as the UEFI boot menu has been left unchanged. In this case, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the {{ic|bcfg}} command, as described [[Unified Extensible Firmware Interface#bcfg|here]].}}

{{Note|On some systems, the above command will not work properly. It will execute without any visible error, but the UEFI boot menu will not have been correctly updated with a new entry. To determine whether the command executed properly, run {{ic|efibootmgr}} without any arguments and see if a new entry has appeared in the list displayed. If there is no new entry, then it will not be possible to enter rEFInd upon reboot, as the UEFI boot menu has been left unchanged. In this case, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the {{ic|bcfg}} command, as described [[Unified Extensible Firmware Interface#bcfg|here]].}}

Next, while using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:

+

Next, while using a manually created {{ic|grub.cfg}} is absolutely fine, it is 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.}}

{{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.}}

Line 781:

Line 759:

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

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

−

{{Note|{{ic|grub-install}} should create a new entry in the UEFI boot menu. If it doesn't, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the {{ic|bcfg}} command, as described [[Unified Extensible Firmware Interface#bcfg|here]].}}

+

{{Note|{{ic|grub-install}} should create a new entry in the UEFI boot menu. If it does not, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the {{ic|bcfg}} command, as described [[Unified Extensible Firmware Interface#bcfg|here]].}}

Installation

You are now presented with a shell prompt, automatically logged in as root.

Change the language

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.

By default, the keyboard layout is set to us. If you have a non-US keyboard layout, run:

# loadkeys layout

...where layout can be fr, uk, be-latin1, etc. See here for a comprehensive list.

The font should also be changed, because most languages use more glyphs than the 26 letter 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:

# setfont Lat2-Terminus16

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 # in front of the locale you want from /etc/locale.gen, along with English (US). Please choose the UTF-8 entry.

Establish an internet connection

Warning: udev no longer assigns network interface names according to the wlanX and ethX naming scheme. If you are coming from a different distribution or are reinstalling Arch and not aware of the new interface naming style, please do not assume that your wireless interface is named wlan0, or that your wired interface is named eth0. You can use the command ip addr show to discover the names of your interfaces.

From systemd-197's release and onward, udev now assigns predictable, stable network interface names that deviate from the legacy incremental naming scheme (wlan0, wlan1, etc.). These interface names are guaranteed to be persistent across reboots, which solves the problem of the lack of predictability of network interface name assignment. For more information about why this was necessary, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .

The 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...

If you get a ping: unknown host error, first check if there is any problem with your cable (or if you have enough wireless signal), otherwise you will need to set up the network manually, as explained below.

In this example, the Ethernet interface is enp2s0f0. If you are unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be "lo" or start with the letter "w". You can also use iwconfig and see which interfaces are not wireless:

In this example, wlp3s0 is the available wireless interface. If you are unsure, your wireless interface is likely to start with the letter "w", and unlikely to be "lo" or start with the letter "e".

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.

Bring the interface up with:

# ip link set wlp3s0 up

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:

# ip link set wlp3s0 up

SIOCSIFFLAGS: No such file or directory

If unsure, invoke dmesg to query the kernel log for a firmware request from the wireless chipset.

Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:

# dmesg | grep firmware

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.

Warning: Wireless chipset firmware packages (for cards which require them) are pre-installed under /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.

The recommendation for a system that will boot via UEFI rather than MBR legacy boot is to format the drive using a GPT partition table. This means that if the drive was previously already partitioned with an MBR (MSDOS) partition table it will now have a new partition table created which will destroy all other data on the drive. Once the new partition table has been created on a drive, only then can individual partitions be created with any chosen format type. When using Gparted, selecting the option to create a new partition table gives an "msdos" partition table by default. If you are intending to follow the advice to create a GPT partition table then you need to choose "Advanced" and then select "gpt" from the drop-down menu. This cannot be done if you have a pre-existing Windows installation on the drive which you wish not to destroy. It is therefore extremely important to not change the partition table to GPT if you intend on having a dual boot system. Leave the Windows install untouched and try to get the Linux install working with UEFI on a drive that contains an MBR (legacy) partition table.

In addition, some newer computers come pre-installed with Windows 8 which will be using Secure Boot. Arch Linux currently does not support Secure Boot, but some Windows 8 installations have been seen not to boot if Secure Boot is turned off in the BIOS. In some cases it is necessary to turn off both Secure Boot as well as Fastboot in the BIOS options in order to allow Windows 8 to boot without Secure Boot. However there are potential security risks in turning off Secure Boot for booting up Windows 8. Therefore, it may be a better option to keep the Windows 8 install intact and have an independent hard drive for the Linux install - which can then be partitioned from scratch using a GPT partition table. Once that is done, creating several ext4/FAT32/swap partitions on the second drive may be a better way forward if the computer has two drives available. This is often not easy or possible on a small laptop. Currently, Secure Boot is still not in a fully stable state for reliable operation, even for Linux distributions that support it.

See Swap for details if you wish to set up a swap partition or swap file. A swap file is easier to resize than a partition and can be created at any point after installation, but cannot be used with a Btrfs filesystem.

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 an extra BIOS Boot Partition. Syslinux does not need one.

Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.

If you would like to start over, you can simply select Quit (or press Template:Keypress) to exit without saving changes and then restart cfdisk (or cgdisk).

If you are satisfied, choose Write (or press Template:Keypress) to finalize and to write the partition table to the drive. Type "yes" and choose Quit (or press Template:Keypress) to exit without making any more changes.

Simply partitioning is not enough; the partitions also need a filesystem. To format the partitions with an ext4 filesystem:

Warning: Double check and triple check that it is actually /dev/sda1 and /dev/sda2 that you want to format. You can use lsblk to help with this.

# mkfs.ext4 /dev/sda1
# mkfs.ext4 /dev/sda2

If you have made a partition dedicated to swap (code 82), do not forget to format and activate it with:

# mkswap /dev/sdaX
# swapon /dev/sdaX

Mount the partitions

Each partition is identified with a number suffix. For example, sda1 specifies the first partition of the first drive, while sda designates the entire drive.

To display the current partition layout:

# lsblk /dev/sda

Note: Do not mount more than one partition to the same directory. And pay attention, because the mounting order is important.

First, mount the root partition on /mnt. Following the example when using cfdisk above (yours may be different), it would be:

# mount /dev/sda1 /mnt

Then mount the home partition and any other separate partition (/boot, /var, etc), if you have any:

# mkdir /mnt/home
# mount /dev/sda2 /mnt/home

In case you have a UEFI motherboard, mount the UEFI partition:

# mkdir -p /mnt/boot/efi
# mount /dev/sdaX /mnt/boot/efi

Select a mirror

Before installing, you may want to edit the mirrorlist file and place your preferred mirror first. A copy of this file will be installed on your new system by pacstrap as well, so it is worth getting it right.

If you want, you can make it the only mirror available by getting rid of everything else (using Template:Keypress), but it is usually a good idea to have a few more, in case the first one goes offline.

Tip:

Use the Mirrorlist Generator to get an updated list for your country. HTTP mirrors are faster than FTP, because of something called 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 Sorting mirrors and Reflector.

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:

Whenever in the future you change your list of mirrors, always remember to force pacman to refresh all package lists with pacman -Syy. This is considered to be good practice and will avoid possible headaches. See Mirrors for more information.

If you are using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see FS#22510). Therefore it is advised to obtain the latest mirror information as described above.

Some issues have been reported in the Arch Linux forums regarding network problems that prevent pacman from updating/synchronizing repositories (see [1] and [2]). 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

The -i switch can be omitted if you wish to install every package from the base group without prompting.

# pacstrap -i /mnt base

Note: If pacman fails to verify your packages, check the system time with cal. If the system date is invalid (e.g. it shows the 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 ntp client, and retry running the pacstrap command. Refer to Time page for more information on correcting system time.

Note: If pacman complains that error: failed to commit transaction (invalid or corrupted package), run the following command:

# pacman-key --init && pacman-key --populate archlinux

This will give you a basic Arch system. Other packages can be installed later using pacman.

Generate an fstab

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 -U option with -L.

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

Warning: The fstab file should always be checked after generating it. If you encounter errors running genfstab or later in the install process, do not run genfstab again; just edit the fstab file.

A few considerations:

Only the root (/) partition needs 1 for the last field. Everything else should have either 2 or 0 (see fstab#Field definitions).

Chroot and configure the base system

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.

Locale

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: locale.gen and locale.conf.

The locale.gen file is empty by default (everything is commented out) and you need to remove the # in front of the line(s) you want. You may uncomment more lines than just English (US), as long as you choose their UTF-8 encoding:

# nano /etc/locale.gen

en_US.UTF-8 UTF-8
de_DE.UTF-8 UTF-8

# locale-gen

This will run on every glibc upgrade, generating all the locales specified in /etc/locale.gen.

The locale.conf file does not exist by default. Setting only LANG should be enough. It will act as the default value for all other variables.

# echo LANG=en_US.UTF-8 > /etc/locale.conf
# export LANG=en_US.UTF-8

Note: If you set some other language than English (US) at the beginning of the install, the above commands would be something like:

# echo LANG=de_DE.UTF-8 > /etc/locale.conf
# export LANG=de_DE.UTF-8

To use other locales for other LC_* variables, run locale to see the available options and add them to locale.conf. It is not recommended to set the LC_ALL variable. An advanced example can be found here.

Console font and keymap

If you set a keymap at 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 vconsole.conf:

# nano /etc/vconsole.conf

KEYMAP=de-latin1
FONT=Lat2-Terminus16

KEYMAP – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.

FONT – Available alternate console fonts reside in /usr/share/kbd/consolefonts/. The default (blank) is safe, but some foreign characters may show up as white squares or as other symbols. It is recommended that you change it to Lat2-Terminus16, because according to /usr/share/kbd/consolefonts/README.Lat2-Terminus16, it claims to support "about 110 language sets".

Possible option FONT_MAP – Defines the console map to load at boot. Read man setfont. Removing it or leaving it blank is safe.

Warning: Using localtime may lead to several known and unfixable bugs. However, there are no plans to drop support for localtime.

# hwclock --systohc --localtime

If you have (or planning on having) a dual boot setup with Windows:

Recommended: Set both Arch Linux and Windows to use UTC. A quick 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.

Not recommended: Set Arch Linux to localtime and disable any time-related services, like 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 DST kicks in. So please do not 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.

Kernel modules

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.

For kernel modules to load during boot, place a *.conf file in /etc/modules-load.d/, with a name based on the program that uses them.

# nano /etc/modules-load.d/virtio-net.conf

# Load 'virtio-net.ko' at boot.
virtio-net

If there are more modules to load per *.conf, the module names can be separated by newlines. A good example are the VirtualBox Guest Additions.

Empty lines and lines starting with # or ; are ignored.

Hostname

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 above, except we are going to make it persistent and automatically run at boot.

Wired

Warning: A bug has been noted in the install ISO, in which the name your interface has during installation differs from the one it will have upon reboot. See FS#33923 for more details.
Use the command ip link (shows interface names) after rebooting into your installed system to find out if you are affected by this. If so, you will have to redo the configuration described below with the correct interface name.

Dynamic IP

Using dhcpcd

If you only use a single fixed wired network connection, you do not need a network management service and can simply enable the dhcpcd service. Here, interface_name is your wired interface:

# systemctl enable dhcpcd@interface_name.service

Using netctl

Copy a sample profile from /etc/netctl/examples to /etc/netctl/:

# cd /etc/netctl
# cp examples/ethernet-dhcp .

Edit the profile as needed (modify Interface):

# nano ethernet-dhcp

Enable the ethernet-dhcp profile:

# netctl enable ethernet-dhcp

Using netctl-ifplugd

Alternatively, you can use netctl's netctl-ifplugd, which gracefully handles dynamic connections to new networks:

After finishing the rest of this installation and rebooting, you can connect to the network with wifi-menu interface_name (where interface_name is the interface of your wireless chipset), which will generate a profile file in /etc/network.d named after the SSID. There are also templates available in /etc/network.d/examples/ for manual configuration.

# wifi-menu interface_name

Warning: If you are using wifi-menu, this must be done *after* your reboot when you are no longer chrooted. The process spawned by this command will conflict with the one you have running outside of the chroot. Alternatively, you could just configure a network profile manually using the templates previously mentioned so that you do not have to worry about using wifi-menu at all.

Enable the net-auto-wireless service, which will connect to known networks and gracefully handle roaming and disconnects:

# systemctl enable net-auto-wireless.service

Note: From Netcfg#Net-Auto-Wireless: wireless-wpa-config profiles do not work with net-auto-wireless. Convert them to wireless-wpa-configsection or wireless-wpa instead.

Note:Netcfg also provides net-auto-wired, which can be used in conjunction with net-auto-wireless.

Note: Wpasupplicant could be fail with message "WPA Authentication/Association Failed". In that case, see this link for a solution.

Make sure that the correct wireless interface (e.g. wlp3s0) is set in /etc/conf.d/netcfg:

# nano /etc/conf.d/netcfg

WIRELESS_INTERFACE="wlp3s0"

It is also possible to define a list of network profiles that should be automatically connected, using the AUTO_PROFILES variable in /etc/conf.d/netcfg. If AUTO_PROFILES is not set, all known wireless networks will be tried.

Analog modem, ISDN or PPoE DSL

Create an initial ramdisk environment

Tip: Most users can skip this step and use the defaults provided in mkinitcpio.conf. The initramfs image (from the /boot folder) has already been generated based on this file when the linux package (the Linux kernel) was installed earlier with pacstrap.

Here you need to set the right hooks if the root is on a USB drive, if you use RAID, LVM, or if /usr is on a separate partition.

Edit /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 virt-manager) may need virtio modules in mkinitcpio.conf to be able to boot.

# nano /etc/mkinitcpio.conf

MODULES="virtio virtio_blk virtio_pci virtio_net"

Set the root password

Set the root password with:

# passwd

Install and configure a bootloader

For BIOS motherboards

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.

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 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.

Syslinux

Install the syslinux package and then use the syslinux-install_update script to automatically install the files (-i), mark the partition active by setting the boot flag (-a), and install the MBR boot code (-m):

Note: If you have partitioned the drive as GPT, install gptfdisk package, as well (pacman -S gptfdisk), because it contains sgdisk, which will be used to set the GPT-specific boot flag.

# pacman -S syslinux
# syslinux-install_update -i -a -m

Configure 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 /dev/sda3 to reflect your root partition (if you partitioned your drive as in the example, your root partition is sda1). Do the same for the fallback entry.

For UEFI motherboards

For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or larger, type EF00, formatted with FAT32) must be present and mounted on /boot/efi. If you have followed this guide from the beginning, you have already done all of these.

While there are other UEFI bootloaders available, using EFISTUB is recommended. Below are instructions for setting up EFISTUB and GRUB (of course you choose only one of them).

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 grub-efi-x86_64. The steps below set up rEFInd to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. Alternative EFISTUB boot managers can be found on the page UEFI Bootloaders#Booting EFISTUB. Both rEFInd and gummiboot can detect Windows UEFI bootloaders in case of dual-boot.

1. Mount the UEFI System Partition on /mnt/boot/efi and chroot back into /mnt.

Note: On some systems, the above command will not work properly. It will execute without any visible error, but the UEFI boot menu will not have been correctly updated with a new entry. To determine whether the command executed properly, run efibootmgr without any arguments and see if a new entry has appeared in the list displayed. If there is no new entry, then it will not be possible to enter rEFInd upon reboot, as the UEFI boot menu has been left unchanged. In this case, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the bcfg command, as described here.

GRUB

Note: In case you have a system with 32-bit EFI, like pre-2008 Apple Macs, install grub-efi-i386 instead of grub-efi-x86_64.

Next, while using a manually created grub.cfg is absolutely fine, it is recommended that beginners automatically generate one:

Tip: To automatically search for other operating systems on your computer, install os-prober (pacman -S os-prober) before running the next command.

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

Note:grub-install should create a new entry in the UEFI boot menu. If it does not, you will instead have to enter the UEFI shell and manually add an entry to the UEFI boot menu with the bcfg command, as described here.