We ❤️ Open Source
A community education resource
How to install CachyOS manually, the Arch Linux way with LVM and encryption
Full CachyOS performance, with Arch-style control: LUKS encryption, LVM, and systemd-boot.
CachyOS is a popular, performance focused Linux distribution based on Arch Linux. CachyOS has been gaining a lot of popularity lately for its speed and modern hardware support, which has drawn the attention of several Linux and gaming enthusiasts.
At the core, CachyOS is Arch Linux, offering the same rolling release model, but it also includes several features and benefits compared to a regular Arch Linux based install, such as:
- Custom Linux kernels optimized for desktop and gaming experiences
- Performance enhancements via optimized packages, compiled for specific CPU’s
- Improved desktop responsiveness through custom CPU schedulers
- Pre-configured settings for common applications and desktop environments
- Gaming packages and configuration
CachyOS also offers a simplified, GUI driven installation process that makes it easy to get started.
However, the goal of this post is to walk you through installing CachyOS the manual, Arch Linux style way using the command line.
Why install CachyOS manually: control, LVM, and learning
By default, CachyOS uses the Calamares installer framework. While this installer makes setup easy, ideal for beginner Linux users, it’s also opinionated. More advanced users may want greater control over how their system is built.
I’ve been using Arch Linux as my daily driver for over 10 years. When I decided to test CachyOS, I wanted a setup that was similar to my Arch Linux setup, including using Logical Volume Manager (LVM) for storage configuration. However, the Calamares installer has some current limitations and does not work with LVM. That’s when I decided to install CachyOS manually.
Installing a Linux distro manually via command-line is also a great learning opportunity. Even if you’re a beginner user, by following this tutorial you can install a Linux distribution from scratch, and get a better understanding of how important components of a Linux system work, including disk partitioning, encryption, Logical Volume Manager (LVM) setup for increased storage flexibility, base system installation, and key configuration steps like generating an initramfs and setting up the bootloader.
By the end, you’ll have a system you can truly call your own, similar to Arch, but with the performance and optimizations benefits of CachyOS.
Let’s get started.
Getting started with the installation media and boot environment
To get started with the installation, download the install media from the official CachyOS download page. You need to copy the ISO file into a bootable pen drive if you’re planning to install on hardware. You can use USB flash tool like Balena Etcher or Ventoy.
For this tutorial, I am using a Virtual Machine and the disk device identifier is /dev/vda. Adapt this for your own case. For example, for a laptop with NVMe drive, the identifier is usually /dev/nvme0n1.
WARNING: This tutorial assumes a blank disk with no data. If you’re using a disk that contains data or another operating system, by following this tutorial you will lose data. Backup first or ensure you’re using a new empty disk.
Boot your system using the installation media via the USB drive you created. You need to enable alternative boot media during startup and the procedure varies for each system. Usually pressing ENTER or ESC during boot brings up a boot selection screen that allows selecting alternative boot media.
If your system has Secure Boot enabled, you first need to disable it on your BIOS to allow the CachyOS media to boot properly.
On the boot screen select CachyOS to boot up the installation environment. If you’re having issues to boot and you’re using old hardware, reboot and select the option “CachyOS Legacy Hardware”:

You need to have access to the network to perform the install and download packages from the Internet. If you’re connected via Ethernet, you should be good to go. If you need WiFi, right click the Network icon on the task bar and select “Configure Network Connections…”:

Then add a new network connection with the “+” button and select “Wi-Fi”. Configure your WiFi network according to your requirements.

Since we’re installing CachyOS via command line, open a terminal by selecting the CachyOS menu, and selecting “Konsole”.

On your newly open terminal, run sudo -i to login as the root user. You need root permissions to perform all steps for the installation:
[liveuser@CachyOS ~]$ sudo -i
[root@CachyOS ~]#
This tutorial assumes you’re running a system that supports UEFI – Unified Extensible Firmware Interface for operating system boot. Ensure you’re running UEFI with this command:
[root@CachyOS ~]# cat /sys/firmware/efi/fw_platform_size
64
Test the network connection by pinging a known Internet address, such as 1.1.1.1. If this command fails, ensure you network configuration is correct.
[root@CachyOS ~]# ping -c 2 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=11.3 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=53 time=12.3 ms
--- 1.1.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1006ms
rtt min/avg/max/mdev = 11.283/11.813/12.344/0.530 ms
You’re ready to partition your disk and configure storage.
Partitioning, encrypting, and configuring LVM storage
Here is where the CachyOS installation really starts. You need at least two partitions: a boot partition – where the kernel and EFI bootloader files reside for booting the system, and a root partition – to store all your Linux system and user files.
Even though the tutorial uses a Virtual Machine, let’s reproduce the procedure used to deploy CachyOS on a laptop computer and encrypt the root partition to protect the data in case of loss or theft. As discussed before we’re also going to use LVM – Logical Volume Manager to increase the storage flexibility, enabling volumes to be expanded or added as required.
Start by partitioning the disk using gdisk. Make sure to use the correct device path identifier for your disk, for example /dev/nvme0n1 for a typical NVMe drive. For the example virtual machine in this tutorial use /dev/vda.
[root@CachyOS ~]# gdisk /dev/vda
Press n to create a new partition and type 1 for the first partition. Press Enter to accept the default start sector and type +1024M to assign 1GB of space for the partition. Use code ef00 to create an EFI boot partition:
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-67108830, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-67108830, default = 67106815) or {+-}size{KMGTP}: +1024M
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): ef00
Changed type of partition to 'EFI system partition'
Next, type n again to create the second partition. You can press Enter four times to use the default values and create a Linux partition using the rest of the space on the disk:
Command (? for help): n
Partition number (2-128, default 2): 2
First sector (34-67108830, default = 2099200) or {+-}size{KMGTP}:
Last sector (2099200-67108830, default = 67106815) or {+-}size{KMGTP}:
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'
Then, press w and Y to write and confirm the new partition layout:
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/vda.
The operation has completed successfully.
You can use the command lsblk to verify the current disk layout:
[root@CachyOS ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2.6G 1 loop /run/archiso/airootfs
sr0 11:0 1 2.8G 0 rom /run/archiso/bootmnt
zram0 253:0 0 3.8G 0 disk [SWAP]
vda 254:0 0 32G 0 disk
├─vda1 254:1 0 1G 0 part
└─vda2 254:2 0 31G 0 part
Format the first partition with the vfat format required by the UEFI boot system:
[root@CachyOS ~]# mkfs.fat -F 32 /dev/vda1
mkfs.fat 4.2 (2021-01-31)
Now, let’s encrypt the second partition using LUKS. Use the command cryptsetup to encrypt the entire second partition:
[root@CachyOS ~]# cryptsetup luksFormat /dev/vda2
WARNING!
========
This will overwrite data on /dev/vda2 irrevocably.
Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/vda2:
Verify passphrase:
To continue the installation and add LVM to the disk, you first need to open the encrypted partition using cryptsetup open. Specify the device to open, e.g. /dev/vda2 and a name to open the device as, such as cryptlvm. Later you can reference this device as /dev/mapper/cryptlvm:
[root@CachyOS ~]# cryptsetup open /dev/vda2 cryptlvm
Enter passphrase for /dev/vda2:
Use lsblk again to see the new “virtual” device cryptlvm:
[root@CachyOS ~]# lsblk /dev/vda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
vda 254:0 0 32G 0 disk
├─vda1 254:1 0 1G 0 part
└─vda2 254:2 0 31G 0 part
└─cryptlvm 252:0 0 31G 0 crypt
Next, setup LVM on this disk by using the command vgcreate. You can use any name for your volume group. In this example, we’re using rootvg:
[root@CachyOS ~]# vgcreate rootvg /dev/mapper/cryptlvm
Physical volume "/dev/mapper/cryptlvm" successfully created.
Volume group "rootvg" successfully created
LVM adds a great flexibility to your storage, allowing you to create different logical volumes (pseudo partitions) without having to re-partition the actual disk. These logical volumes can be created, deleted, and expanded dynamically according to your needs. Use vgs to see the new volume group rootvg created:
[root@CachyOS ~]# vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 1 0 0 wz--n-- 30.98g 30.98g
Now, create a logical volume for the root partition with 10GB of space to store all CachyOS system files. This is enough for the basic install. Remember that you can expand this volume later if you need more space to install additional packages:
[root@CachyOS ~]# lvcreate -n root -L 10G rootvg
Logical volume "root" created.
Create another logical volume for the home partition, to store all user files. This is a good practice to keep user files separated from system files:
[root@CachyOS ~]# lvcreate -n home -L 10G rootvg
Logical volume "home" created.
You can also create dedicated volumes for other purposes such as logging, and applications. For now, let’s use only these two volumes.
Create an ext4 file system for the root volume:
[root@CachyOS ~]# mkfs.ext4 /dev/mapper/rootvg-root
Then create another ext4 file system for the home volume:
[root@CachyOS ~]# mkfs.ext4 /dev/mapper/rootvg-home
Now, you need to mount the root volume under /mnt so we can bootstrap the system:
[root@CachyOS ~]# mount /dev/mapper/rootvg-root /mnt
Create the directories for the boot and home file systems on /mnt:
[root@CachyOS ~]# mkdir -p /mnt/{boot,home}
Next, mount the home volume as /mnt/home:
[root@CachyOS ~]# mount /dev/mapper/rootvg-home /mnt/home/
And, finally, mount the boot partition under /mnt/boot:
[root@CachyOS ~]# mount /dev/vda1 /mnt/boot/
Use the command lsblk one last time to ensure your disk layout is correct with all required partitions and volumes mounted on their appropriate location:
[root@CachyOS ~]# lsblk /dev/vda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
vda 254:0 0 32G 0 disk
├─vda1 254:1 0 1G 0 part /mnt/boot
└─vda2 254:2 0 31G 0 part
└─cryptlvm 252:0 0 31G 0 crypt
├─rootvg-root 252:1 0 10G 0 lvm /mnt
└─rootvg-home 252:2 0 10G 0 lvm /mnt/home
Your storage layout is complete and your disk ready to receive the new CachyOS system. But before we download files, let’s configure the package repositories.
Configuring CachyOS CPU-optimized repositories
As discussed before, as one of its main benefits, CachyOS compiles and optimizes packages for specific CPU micro-architectures, such as x86-64 v3, x86-64 v4, or AMD znver4. By using packages that align with your CPU, you benefit from specific CPU instructions that can give your machine a performance boost. The performance enhancement varies from a few percentage points to something considerable (5% to 30%) depending on your CPU and workloads.
For more information about the optimized repositories, consult the official CachyOS Optimized Repositories documentation.
The GUI installer automatically selects the correct optimized repo, depending on your CPU. In this case, we need to configure the repository manually. First, you need to determine what is your CPU architecture. For the main x86-64 architecture run this command to find supported architectures:
[root@CachyOS ~]# /lib/ld-linux-x86-64.so.2 --help | grep supported
x86-64-v4 (supported, searched)
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
If you’re running a recent AMD Ryzen CPU, also run the following command to determine if it’s compatible with the znver4 instruction set:
[root@CachyOS ~]# gcc -march=native -Q --help=target 2>&1 | grep -Po "^\s+-march=\s+\K(\w+)\$"
znver4
If your CPU supports only x86-64-v2 architecture then your pacman.conf file is already configured correctly and you can skip this section.
For other architectures, configure the optimized repos by editing the file pacman.conf with nano and adding the correct repos, according to your CPU compatibility. Add one of these blocks to pacman.conf before the configuration line for the [cachyos] repo.
For example, for znver4 compatible AMD CPUs:
[root@CachyOS ~]# nano /etc/pacman.conf
[cachyos-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
[cachyos-core-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
[cachyos-extra-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
Or for x86-64-v4 CPUs, add this configuration:
[root@CachyOS ~]# nano /etc/pacman.conf
[cachyos-v4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
[cachyos-core-v4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
[cachyos-extra-v4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist
Finally, if your CPU supports x86-64-v3, add this:
[root@CachyOS ~]# nano /etc/pacman.conf
[cachyos-v3]
Include = /etc/pacman.d/cachyos-v3-mirrorlist
[cachyos-core-v3]
Include = /etc/pacman.d/cachyos-v3-mirrorlist
[cachyos-extra-v3]
Include = /etc/pacman.d/cachyos-v3-mirrorlist
Save the configuration file and quit by pressing ctrl+X then Y, and Enter to confirm the file name.
Next, run the command cachyos-rate-mirrors to find the fastest mirrors according to your location to ensure fast package downloads:
[root@CachyOS ~]# cachyos-rate-mirrors
--> Ranking mirrors for arch repository in /etc/pacman.d/mirrorlist...
# STARTED AT: 2026-03-20 04:06:59.711409463 +00:00
...
# FINISHED AT: 2026-03-20 04:07:24.711213807 +00:00
If you added an optimized repository to your pacman.conf file, clean and rebuild the package cache with pacman -Scc and pacman -Sy to ensure you will download the correct packages for your architecture:
[root@CachyOS ~]# pacman -Scc
warning: database file for 'cachyos-znver4' does not exist (use '-Sy' to download)
warning: database file for 'cachyos-core-znver4' does not exist (use '-Sy' to download)
warning: database file for 'cachyos-extra-znver4' does not exist (use '-Sy' to download)
Cache directory: /var/cache/pacman/pkg/
:: Do you want to remove ALL files from cache? [y/N] y
removing all files from cache...
Database directory: /var/lib/pacman/
:: Do you want to remove unused repositories? [Y/n] y
removing unused sync repositories...
Now, rebuild the cache:
[root@CachyOS ~]# pacman -Sy
You’re now ready to bootstrap your new system.
Bootstrapping your CachyOS base system with pacstrap
Bootstrap your new CachyOS system by using pacstrap to install a minimal set of packages into the new root partition mounted under /mnt. Only the base package group is required but it’s also a good idea to add a few other packages to make configuration easier in the following steps. In this case, add a text editor like neovim, development packages base-devel, and the CachyOS repositories mirror lists.
[root@CachyOS ~]# pacstrap -K /mnt base base-devel nvim cachyos-keyring cachyos-mirrorlist cachyos-v3-mirrorlist cachyos-v4-mirrorlist
You could also add other packages likes the Linux kernel and hardware firmware but we’ll do that in a later step. Next, copy the pacman.conf configuration file from the installer environment into the new system to keep the configuration you added for the optimized CachyOS repos:
[root@CachyOS ~]# cp /etc/pacman.conf /mnt/etc/pacman.conf
Then, use the genfstab command with the -U flag to auto-generate the fstab entries for the new system using the partition’s UUID. This allows the future system to correctly mount the filesystems during boot:
[root@CachyOS ~]# genfstab -U /mnt >> /mnt/etc/fstab
Finally use the arch-chroot command to switch your environment to the new system root partition:
[root@CachyOS ~]# arch-chroot /mnt
You’re now connected to your new system and can perform some basic system configurations.
Essential system configuration: locale, timezone, and networking
Let’s start configuring some required or just useful system parameters. First, add your timezone to display the time correctly. Look for available time zones at /usr/share/zoneinfo/. For example, for the Toronto (EST) timezone, use this command:
[root@CachyOS /]# ln -sf /usr/share/zoneinfo/America/Toronto /etc/localtime
Then synchronize the time to the hardware clock:
[root@CachyOS /]# hwclock --systohc
Next, select the correct locale for your language so the system display language and date format correctly for your language. Edit the file /etc/locale.gen and uncomment the lines associated with your location / language. For example for Canada and English, uncomment the lines starting with en_CA. You can also uncomment more languages to enable additional locales:
[root@CachyOS /]# nvim /etc/locale.gen
Save and quit the file, and generate the locales using the command locale-gen:
[root@CachyOS /]# locale-gen
Generating locales...
en_CA.UTF-8... done
en_CA.ISO-8859-1... done
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.
Then, select the default locale for your system by adding a corresponding entry into /etc/locale.conf. For example, to set the default language for Canada’s English, use en_CA.UTF-8:
[root@CachyOS /]# nvim /etc/locale.conf
LANG=en_CA.UTF-8
Next select a console keyboard layout. This is not required but it’s particularly important if you have a non-English keyboard as it impacts the keyboard configuration during boot allowing you to correctly type your encryption password. You can find keyboard layouts in /usr/share/kbd/keymaps/i386/:
[root@CachyOS /]# nvim /etc/vconsole.conf
KEYMAP=us-acentos
Define your system’s host name by adding it to /etc/hostname:
[root@CachyOS /]# nvim /etc/hostname
Now, run the command cachyos-rate-mirrors again to update the mirror list according to your location for the new system. You did this before but the configuration was valid only for the install environment, not the newly installed system. First, install the cachyos-rate-mirrors package:
[root@CachyOS /]# pacman -S cachyos-rate-mirrors
Then, run the command to update the list:
[root@CachyOS /]# cachyos-rate-mirrors
Install Network Manager to allow the network configuration on the new system after boot, including WiFi configuration. You can also use an alternative manager, like systemd-networkd, if you prefer. Since you have the CachyOS optimized repositories configured, pacman asks you from which repository you want to install the package, in case it’s available in more than one. In general, select the optimized CachyOS repository for your architecture to benefit from the performance optimizations done by the CachyOS team:
[root@CachyOS /]# pacman -S networkmanager
resolving dependencies...
:: There are 2 providers available for libpolkit-gobject-1.so=0-64:
:: Repository cachyos-extra-znver4
1) polkit
:: Repository extra
2) polkit
Enter a number (default=1): 1
Now, enable the NetworkManager service to start automatically during boot:
[root@CachyOS /]# systemctl enable NetworkManager
Created symlink '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' → '/usr/lib/systemd/system/NetworkManager.service'.
Created symlink '/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service' → '/usr/lib/systemd/system/NetworkManager-dispatcher.service'.
Created symlink '/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service' → '/usr/lib/systemd/system/NetworkManager-wait-online.service'.
Your basic configuration is complete and your system is almost ready to use. Next, let’s install a Linux kernel.
Choosing and installing the right CachyOS Linux kernel
CachyOS provides many choices for the Linux kernel for your system. These options have several differences in patches and I/O scheduler used, as well as, which optimizations they applied. For a full list of all the options available consult the CachyOS Kernel page. Use this information to decide which kernel to use according to your needs.
For this tutorial, and as a good general option, use the standard linux-cachyos package. It’s the default option the CachyOS developers recommend if you don’t have any specific requirements. This kernel already comes with several patches targeted for Desktop users and includes several optimizations.
It’s also recommended to include the CPU microcode package for your CPU type. Choose between intel-ucode or amd-ucode depending on your CPU vendor.
In addition to the kernel and microcode, you also need a few other important packages:
- linux-firmware – Includes hardware firmware for several hardware components, including GPU’s and WiFi cards.
- lvm2 – LVM tools required to use Logical Volume Manager storage.
- cachyos-hooks – CachyOS hooks for
pacmanand branding. - cachyos-settings – Includes additional settings recommended by CachyOS such as zram generator and Ananicy rules to optimize process prioritization.
[root@CachyOS /]# pacman -S linux-cachyos linux-firmware amd-ucode lvm2 cachyos-hooks cachyos-settings
Next, configure the file /etc/mkinitcpio.conf to customize your initramfs. The initramfs ensures your system can boot properly by adding required modules to the Linux kernel. Since we’re using disk encryption and LVM, you need to add these modules to the HOOKS list to include these components during boot:
[root@CachyOS /]# nvim /etc/mkinitcpio.conf
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole sd-encrypt block lvm2 filesystems fsck)
Generate the new initramfs:
[root@CachyOS /]# mkinitcpio -P
Finally, define a password for the root user to be able to log into the new system after boot.
[root@cachyos01 /]# passwd
Exit from the current environment and go back to the installation environment.
[root@CachyOS boot]# exit
The last step for the installation is to configure a boot loader.
Setting up the systemd-boot bootloader for UEFI and LUKS
To boot a Linux system you need to configure a Linux compatible boot loader. CachyOS and Arch Linux provide several options. By installing manually you can use the option that is most convenient to you according to your requirements. You can see a complete list of supported boot loaders on the CachyOS documentation.
I particularly like to use UKI – Unified kernel image booted directly from the UEFI firmware, but that will be a topic for another post.
For now, let’s use systemd-boot a capable and easy to configure Linux boot loader for UEFI systems.
To configure systemd-boot you need to use arch-chroot with the -S flag to switch back to your new system environment using systemd:
[root@cachyos01 ~]# arch-chroot -S /mnt
systemd-boot is already installed on the system with systemd and no additional packages are required. Install the boot loader using bootctl:
[root@cachyos01 /]# bootctl install
Next, configure an entry on the boot loader by editing the file /boot/loader/loader.conf. Add a default entry pointing to a new file cachyos.conf that you’ll create in the next step:
[root@cachyos01 boot]# nvim /boot/loader/loader.conf
default cachyos.conf
Get the UUID of your encrypted partition to add the boot loader configuration:
[root@CachyOS /]# blkid | grep crypto_LUKS
/dev/vda2: UUID="cf6f268b-9726-4daa-a4c9-f05713eda2a4" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="1ecc49d3-0283-435c-9393-2ec64a952900"
Finally, create the cachyos.conf boot loader entry with these options. Replace <LUKS_PART_UUID> with the actual UUID for your LUKS encrypted partition obtained from the command above. For example, for this tutorial the UUID is cf6f268b-9726-4daa-a4c9-f05713eda2a4:
[root@cachyos01 entries]# nvim /boot/loader/entries/cachyos.conf
title CachyOS
linux /vmlinuz-linux-cachyos
initrd /initramfs-linux-cachyos.img
options rd.luks.name=<LUKS_PART_UUID>=cryptlvm root=/dev/rootvg/root rootflags=rw,relatime splash quiet
Now, exit from the new system environment back to the installer again:
[root@cachyos01 /]# exit
exit
Your new system is now ready.
Unmounting and rebooting into your new CachyOS system
Back into the installation environment, unmount all the new system’s file systems before rebooting:
[root@CachyOS ~]# umount -R /mnt
If you get an error saying /mnt is busy, it’s likely the GPG agent holding it. Kill the gpg-agent process and unmount /mnt again:
[root@CachyOS ~]# pkill gpg-agent
[root@CachyOS ~]# umount -R /mnt
Then reboot the machine and it will boot into your new CachyOS system:
[root@CachyOS ~]# reboot
What’s next: users, desktop environments, and Secure Boot
This process of installing the CachyOS Linux manually allowed you to install a bare minimal system that is tailored to your specific needs. By running this install process you added only the packages you needed and configured the system with options that might be otherwise unavailable.
However, there is still things you need to add to your system to make it fully useful, for example:
- Creating a regular user.
- Installing a desktop environment or window manager.
- Enabling Secure Boot.
In the next few weeks I intend to publish follow up articles showing how to perform some of these tasks on your new CachyOS system. Stay tuned!
For more information about the Arch installation process, consult the official Arch Linux Install Guide. For specific information about CachyOS visit the CachyOS Wiki.
More from We Love Open Source
- Pop!_OS 24.04 review: Was the two-year wait for COSMIC Desktop worth it?
- Why open source is critical for the continued advancement of new tech
- My first experience with Manjaro Cinnamon as a Linux Mint user
- The AI slop problem threatening open source maintainers
- Getting started with OpenClaw
The opinions expressed on this website are those of each author, not of the author's employer or All Things Open/We Love Open Source.