• Arch Linux Livecd
• Arch Linux Live Gui

Discussions specifically regarding the Arch Linux distribution and community. NOT generally a place for technical issues unless systemic in nature. ( Moderated by 2ManyDogs, ewaller, fukawi2, HalosGhost, R00KIE, Slithery, V1del, WorMzy, Xyne). The other day I was testing the latest Arch Linux live ISO in VirtualBox. Before installing Arch Linux on disk, I booted into the live system and wanted to try some applications to see how it performs in Arch Linux. As expected, everything worked fine out of the box. I started to install some more applications as well.

• A glorious Arch Linux Live CD. Contribute to mytbk/gloriousarch development by creating an account on GitHub.
• ArchLinux-Live Brought to you by: agordgnulinux. Downloads: 2 This Week Last Update: 2015-03-25. Get project updates, sponsored.

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

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

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

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

Pre-installation

Acquire an installation image

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

Verify signature

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

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

Alternatively, from an existing Arch Linux installation run:

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

Prepare an installation medium

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

Boot the live environment

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

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

Set the keyboard layout

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

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

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

Verify the boot mode

To verify the boot mode, list the efivars directory:

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

Connect to the internet

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

• Ensure your network interface is listed and enabled, for example with ip-link(8):
• For wireless, make sure the wireless card is not blocked with rfkill.
• Connect to the network:
  • Ethernet—plug in the cable.
  • Wi-Fi—authenticate to the wireless network using iwctl.
• Configure your network connection:
  • DHCP: dynamic IP address and DNS server assignment (provided by systemd-networkd and systemd-resolved) should work out of the box for wired and wireless network interfaces.
  • Static IP address: follow Network configuration#Static IP address.
• The connection may be verified with ping:

Update the system clock

Use timedatectl(1) to ensure the system clock is accurate:

To check the service status, use timedatectl status.

Partition the disks

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

Results ending in rom, loop or airoot may be ignored.

The following partitions are required for a chosen device:

• One partition for the root directory/.
• For booting in UEFI mode: an EFI system partition.

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

Example layouts

See also Partitioning#Example layouts.

• Use fdisk or parted to modify partition tables, for example fdisk /dev/the_disk_to_be_partitioned.
• Swap space can be set on a swap file for file systems supporting it.
• If the disk from which you want to boot already has an EFI system partition, do not create another one, but use the existing partition instead.

Format the partitions

Once the partitions have been created, each newly created partition must be formatted with an appropriate file system. For example, to create an Ext4 file system on /dev/root_partition, run:

If you created a partition for swap, initialize it with mkswap(8):

See File systems#Create a file system for details.

Mount the file systems

Mount the root volume to /mnt. For example, if the root volume is /dev/root_partition:

Create any remaining mount points (such as /mnt/efi) using mkdir(1) and mount their corresponding volumes.

If you created a swap volume, enable it with swapon(8):

genfstab(8) will later detect mounted file systems and swap space.

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, after connecting to the internet, reflector updates the mirror list by choosing 70 most recently synchronized HTTPS mirrors and sorting them by download rate.[2]

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

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

Install essential packages

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

• You can substitute linux for a kernel package of your choice, or you could omit it entirely when installing in a container.
• You could omit the installation of the firmware package when installing in a virtual machine or container.

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

• userspace utilities for the management of file systems that will be used on the system,
• utilities for accessing RAID or LVM partitions,
• specific firmware for other devices not included in linux-firmware,
• software necessary for networking,
• a text editor,
• packages for accessing documentation in man and info pages: man-db, man-pages and texinfo.

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

Configure the system

Fstab

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

Arch Linux Livecd

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

Chroot

Change root into the new system:

Time zone

Set the time zone:

Run hwclock(8) to generate /etc/adjtime:

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

Localization

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

Create the locale.conf(5) file, and set the LANG variable accordingly:

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

Network configuration

Create the hostname file:

Add matching entries to hosts(5):

Arch Linux Live Gui

If the system has a permanent IP address, it should be used instead of 127.0.1.1.

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

Initramfs

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

For LVM, system encryption or RAID, modify mkinitcpio.conf(5) and recreate the initramfs image:

Root password

Set the root password:

Boot loader

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

Reboot

Exit the chroot environment by typing exit or pressing Ctrl+d.

Optionally manually unmount all the partitions with umount -R /mnt: this allows noticing any 'busy' partitions, and finding the cause with fuser(1).

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

Post-installation

See General recommendations for system management directions and 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.

I recently built a new computer, using the following hardware:
MB: Gigabyte X570 Aorus Pro Wifi
CPU: AMD Ryzen 5 3400G
PSU: EVGA Supernova 750 GA
HDD: WD Blue 4TB
Memory: 32GB Corsair Vengeance LPX.

About 95% of the time when I try to boot into the live USB the screen goes blank and nothing happens. I've tried setting acpi=off, as well as all the settings here. Turning off acpi seems to get me farther, as then I get the 'Welcome to Arch' Message as well as some more output, but then during the boot up process there is a kernel oops and everything halts. Here is the output: https://i.postimg.cc/X3Qr9Gs9/1202200016a-HDR.jpg. I've tried googling acpi=off causes kernel oops and similar queries, but to no success. I'm at my wits end, and would really appreciate if anyone could help me. Looking at the above message it is hard to tell exactly what is wrong with my limited expertise, but it seems to be a problem with the motherboard. I also updated the BIOS, but to no effect. Every once and a while I will get a successful boot without using acpi=off, but it seems to be happening less and less often. Thus I was able to install arch on the hard drive, and have been playing around with kernel parameters on that rather than the live USB, but both have the same problems so it seems to be something hardware related. I'm really hoping there's some magic kernel parameter that I haven't been able to found thus far that will fix everything, but I'm beginning to lose hope. Thank you for your time and help, and let me know if there's any more info you need from me!

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2020-12-02 13:42:17)