ArcoLinux 24.04


Transitioning to a More Flexible Bootloader Configuration


ArcoLinux is taking significant strides towards enhancing the flexibility and user control over its bootloader configurations. In a recent update, the ArcoLinux team announced a series of changes aimed at improving the installation and booting process. These adjustments come with a focus on providing users with the ability to choose and switch between different bootloader options, specifically GRUB, systemd-boot, and the soon-to-be-available Refind. This article aims to dissect these updates, explaining their implications and how users can navigate through them.

Key Changes and Their Implications:

  1. Install Refind Button NOT in April ISOs: The upcoming April release of ArcoLinux ISOs will NOT have the ‘Install Refind’ button. The May ISOs will have this bootloader option. We need to set the stage for the broader bootloader customization options to be introduced in May.
  2. Splitting Pacman Hooks: A critical component of this transition involves the moving of Pacman hooks into three separate entities. This division allows for a more targeted application of these hooks based on the bootloader choice—GRUB, systemd-boot, or Refind. Each set of hooks is designed to ensure the smooth operation and reliability of its corresponding bootloader.
  3. Enhanced Bootloader Flexibility: Starting May, users will have the option to switch between GRUB, systemd-boot, and Refind seamlessly. This flexibility, however, comes with a cautionary note. The ArcoLinux team emphasizes the importance of understanding your system’s setup before making any changes. Switching bootloaders without a clear understanding of your system’s configuration could lead to complications.
  4. The Importance of Pacman Hooks: Pacman hooks play a pivotal role in maintaining system stability, especially during updates that affect the bootloader. By automating critical processes such as rebuilding the GRUB configuration, these hooks prevent potential boot issues. The upcoming changes aim to retain this safety mechanism while allowing for greater customization.

How to Navigate the Changes:

  • Understanding Your Current Bootloader: Before considering any changes, users should determine their current bootloader configuration. Knowing whether your system uses GRUB or systemd-boot is crucial for a smooth transition.
  • Preparing for the Transition: Users are encouraged to stay informed through ArcoLinux’s communication channels for updates and detailed instructions on how to adopt the new bootloader configurations. The phased implementation ensures users have ample time to understand and prepare for the changes.
  • Safety and Precautions: While the flexibility to switch between bootloaders is a significant advancement, it comes with responsibilities. Users must acknowledge the disclaimer regarding potential system risks and ensure they have a clear understanding of their system’s architecture before making any changes.


The forthcoming changes to ArcoLinux’s bootloader configuration represent a significant step towards giving users more control over their systems. By introducing the ability to choose and switch between different bootloaders, ArcoLinux is not only enhancing its system’s flexibility but also ensuring that safety mechanisms like Pacman hooks continue to protect users. As we approach these changes, it’s crucial for users to stay informed, understand their system’s configuration, and proceed with caution to make the most of these new options.

This is also for the ArcoLinuxD users who have the arcolinuxd-system-config-git package.



Mid April we remove the hooks from the arcolinux(d)-system-config package leaving you exposed to possible bootloader issues IF you did not install the correct new package.

DISCORD has a channel with the latest fixes

For ArcoLinux users, the troubleshooting process is made more efficient through the centralization of important fixes and solutions on Discord, offering an easy way to address any issues that arise.

Don’t miss out on the informative playlists on YouTube, which we suggest bookmarking for quick access:

– A playlist focusing on ArcoLinux fixes.
– A playlist dedicated to the latest ArcoLinux news.
– A playlist highlighting the newest features and updates in ArcoLinux.
– Tips on ensuring a smooth experience with ArcoLinux’s rolling release model.

Together, these resources provide a thorough compilation of vital information and updates.

Arch-chroot into BTRFS system

The video highlights the importance of having an Arch Linux ISO and knowledge of the Arch-chroot method to fix issues in Arch Linux-based systems.

The process involves mounting the root partition and other necessary sub-volumes, such as home, var, log, and cache, to access and fix the system.

The video emphasizes the need to carefully choose which sub-volumes to mount based on the specific issue and requirements.

The tutorial provides step-by-step instructions on how to install the missing kernel package (vmlinuz-linux) and its headers to resolve the “vmlinuz-linux not found issue“.

The video demonstrates the importance of backing up data before attempting any fixes to avoid potential data loss.

The video showcases the usefulness of the Arch-chroot method in troubleshooting and fixing issues in Arch Linux-based systems.

The tutorial provides practical exercises and guidelines to help users understand and apply the Arch-chroot method effectively.


ArcoLinux has released a new script focusing on microcode management.


This script is significant for users who need to ensure their system’s microcode is correctly positioned for optimal performance. The key aspect of this update is the script addition that automatically places the microcode in the correct order in the boot process, specifically behind the autodetect step. This adjustment ensures that the system correctly identifies and applies the appropriate Intel or AMD microcode during boot, depending on the processor type.

Users are encouraged to pay attention to this update and check that the microcode is correctly placed behind the autodetect function.

Whether it is required on your system or not can only be decided and tested by you.

Microcode is a layer of low-level code that operates on the CPU level to correct the processor’s behavior as specified by the manufacturer. It’s essentially a way for manufacturers to fix errors, enhance functionality, or add new features to the CPU without needing to physically modify the hardware. On Arch Linux, as with many Linux distributions, managing CPU microcode updates is an important aspect of system maintenance, particularly for ensuring stability, security, and performance.

The script will install intel-ucode or amd-ucode and set microcode in your /etc/mkinitcpio.conf.

Arch linux and efistub

This video serves as an extensive guide on installing Arch Linux, emphasizing the Arch Linux way and introducing a fourth bootloader option, EFI STUB, alongside GRUB, systemd-boot, and Refind.

The presenter details the process of setting up a system with the new bootloader option, discussing the importance of proper microcode placement and configuring various system settings, including partitioning, file system creation, and time settings.

The tutorial covers the installation of necessary packages, including the Linux kernel and firmware, and explains how to configure the system for internet access, set up a root password, and manage user accounts. Additionally, the video touches on graphical environment setup, specifically installing the Plasma desktop environment, and concludes with the successful reboot of the system using EFI STUB, showcasing a minimal Plasma setup.

This tutorial is a valuable resource for users looking to install Arch Linux with a focus on learning the process and exploring different bootloader options.


When faced with an issue on Arch Linux, there are several effective strategies you can employ to diagnose and resolve the problem. Given Arch Linux’s DIY philosophy, a proactive and informed approach is essential. Here’s a comprehensive guide on how to tackle issues on Arch Linux:

1. Consult the Arch Wiki

The Arch Wiki is a treasure trove of information, offering comprehensive guides, troubleshooting tips, and best practices for virtually every aspect of Arch Linux. It should be your first stop when encountering an issue, as it likely contains detailed instructions for resolution.

2. Use the Arch Forums

The Arch Linux forums are an active community of users and developers. Before posting a new thread, search the forums to see if someone else has encountered a similar issue. If you decide to post, provide detailed information about your problem, including error messages, system logs, and what steps you’ve already taken to try to resolve the issue.

3. Leverage the Arch Linux IRC Channel

For real-time assistance, you can join the Arch Linux IRC channel (#archlinux on Libera.Chat). This can be particularly useful for troubleshooting complex or urgent issues. Similar to the forums, ensure you have all relevant information on hand to share with others who may help.

4. Check the System Journal

The journalctl command is a powerful tool for reviewing system logs. It can provide insights into what went wrong. Use it to look for error messages or warnings that occurred around the time the issue first appeared.

5. Read the Official News

Arch Linux has a rolling release model, meaning updates are continuous and may sometimes cause issues. The Arch Linux home page features official news that can alert you to potential issues with updates and provide solutions or workarounds.

6. Use Arch Linux’s Bug Tracker

If you suspect you’ve encountered a bug, the Arch Linux bug tracker is the place to check if it’s already been reported. If not, you can file a new report. Ensure you follow the guidelines for submitting bugs to make it easier for developers to address the issue.

7. Rollback Packages

Arch Linux’s package manager, pacman, and the Arch User Repository helper tools allow you to rollback packages to a previous version if a recent update is the source of your troubles. The downgrade tool, which can be installed from the AUR, makes this process straightforward. ArcoLinux has an extra one downgrada.

8. Reinstall the Package

Sometimes, simply reinstalling the problematic package can resolve the issue. This can fix problems stemming from corrupted files or improperly configured settings.

9. System Restore with Timeshift

If you have a backup system like Timeshift installed, you can roll back your system to a previous state before the issue occurred. This is particularly useful for undoing the effects of a problematic update.

10. Document and Share Your Solution

If you manage to solve the issue, consider sharing your solution on the appropriate forum, wiki, or social media platform. Documenting your troubleshooting process and solution can help others who might face the same problem.


Troubleshooting issues on Arch Linux requires patience and a willingness to learn. The community resources available are extensive, and with a systematic approach, most problems can be resolved. Always remember to backup your system regularly to avoid data loss during troubleshooting.

What to do when you are confronted with an issue – hands-on example


In mid-March, the application experienced update issues. Given our policy against retaining software that causes frustration on the ISO, it will not be installed by default moving forward. Users may choose to install it post-reboot using Pamac or Octopi, if desired.

sudo pacman -S pamac-aur
sudo pacman -S octopi octopi-notifier-qt5


Following packages were removed from Calamares and Sofirem

  • midori
  • min


We created an extra script in arcolinux-nemesis scripts just for Plasma 6.
Learn how to script and recreate your own look and feel after a clean installation of any distro.


Plasma got a lot of attention with the new Plasma 6 release.

We covered many topics in these 38 videos just on Plasma 6.

Do you build a lot of packages with yay or paru

Here is a video how to remove the ‘debug’ code from the makepkg.conf so you only build the package and not the package-debug variant.



We have created a new icon theme just for Plasma.

Surfn-plasma-dark-breeze – you will see that the folders can change according to the colors of the wallpaper if you change the settings in Plasma.


A comprehensive tutorial has been developed to guide users through the process of cleaning up Grub entries, ensuring a more organized and streamlined boot menu. This guide delves into the specifics of identifying the crucial files involved in configuring Grub, providing clear instructions on their locations and how to effectively modify them. By following this tutorial, users can learn to customize their Grub entries, removing unnecessary ones and keeping their boot menu concise and efficient. This is particularly useful for users looking to enhance their system’s boot time and simplify the boot selection process.

ArcoLinuxB Plasma Development

In light of the recent release of Plasma 6, we’ve developed a selection of packages tailored for this latest version, enhancing the user experience for those on ArcoLinux. This allows users the flexibility to maintain the original Arch Linux aesthetic and functionality, or alternatively, to incorporate these new packages into their setup. The integration of these packages can be seamlessly performed either during the installation process through Calamares—the graphical installer for Linux—or post-installation, using Sofirem, our software management tool.

These custom packages for Plasma 6 are designed to offer additional features and personalizations that go beyond the default Plasma experience, giving users the opportunity to customize their desktop environment to better suit their preferences and workflows. Whether you’re a user who appreciates the sleek, untouched look of vanilla Arch Linux or someone looking to enrich your Plasma 6 environment with enhanced functionality and aesthetic appeal, our newly developed packages provide the means to tailor your system precisely how you see fit.

There is also a meta package to install all of them with one package.

sudo pacman -S arcolinux-meta-plasma-design

ArcoLinuxB Plasma

The default setup referred to here is designed to provide users with a pure, untouched experience, closely mirroring the original Plasma environment as it is found in Arch Linux, without any modifications or enhancements specific to ArcoLinux. This “vanilla” setup ensures that users are presented with the most fundamental version of the Plasma desktop, devoid of any additional themes, widgets, configurations, or customizations that are typically introduced by ArcoLinux.

This approach offers a clean slate for users, particularly those who prefer to start with a minimal base and customize their desktop environment according to their personal preferences. It caters to users who value the simplicity and efficiency of the Plasma desktop in its original form, allowing for a more traditional Arch Linux experience. Users can then decide whether to introduce ArcoLinux’s Plasma customizations at their own pace, tailoring their system’s look and feel and functionality to match their individual needs and tastes. This flexibility in customization and the option to either embrace the vanilla setup or explore ArcoLinux’s enhancements highlight the adaptability and user-centric focus of the ArcoLinux distribution.

Users have access to a selection of packages specifically included for the purpose of “ricing” or customizing the appearance and functionality of their desktop environments. “Ricing,” a term originated from the car modification scene, refers to the process of making aesthetic and functional tweaks to a computer’s graphical user interface, making it visually appealing and potentially more efficient for the user’s needs.

ArcoLinuxB Xtended – nimdow added

The article highlights the straightforward process of integrating a Tiling Window Manager (TWM) into an existing ISO, showcasing the flexibility and educational value of ArcoLinux as a platform. Through the use of Meld, a visual diff and merge tool, the article guides users on how to compare package lists from different ISOs. This comparison allows users to make informed decisions about which packages to include or exclude in their customized ISO, tailoring the operating system to their specific needs and preferences.

The process of burning the newly configured ISO and testing it ensures that users can verify the functionality and compatibility of their customizations, providing a hands-on approach to learning about operating system development. This approach not only teaches users the technical skills needed to modify and enhance an ISO but also instills a deeper understanding of the underlying principles and considerations involved in distribution customization.

ArcoLinux positions itself as akin to a university in the realm of Linux distributions, offering an educational journey through which users can learn to build their own ISOs and distros. This analogy emphasizes the project’s commitment to empowering users with knowledge and skills, moving beyond mere usage to a comprehensive understanding of system architecture, software management, and customization techniques. Through detailed tutorials, documentation, and community support, ArcoLinux provides a learning environment where users can graduate from basic users to proficient developers, capable of creating personalized and optimized Linux distributions.


  1. Git Basics: Introduces Git as a tool for tracking code changes and facilitating developer collaboration, emphasizing its role in managing project history.
  2. Git Workflow: Describes the standard process of using Git, from creating local repositories and making changes to pushing updates to a remote repository. Essential commands include `git clone`, `git add`, `git commit`, and `git push`.

We keep it simple and basic in regards to the git knowledge required. We are also assuming there is no collaboration.

We just want to keep our dotfiles safe.

Halfway through the article we write for the isobuilders or distrobuilders.

  • How to create PKGBUILDS?
  • How to create a repo to host the packages you created with the PKGBUILDS?
  • How to add your personal repo to the ArcoLinux iso and build your personal iso?

Problems installing – have the reflex to use the easy installation

To emphasize once more: Should you run into complications during the advanced installation due to Pacman errors, it’s advisable to switch to the easy installation method.

It’s important to note that these issues stem from Pacman, not the Calamares installer.

The easy installation process is dependable and will ensure a successful setup.

After restarting your system, you’ll find three options for managing your software:

– Sofirem: Provides an easy-to-use interface for installing or uninstalling software, mirroring the capabilities found in the advanced mode of Calamares.
– Custom Scripts: For those seeking a tailored setup, you can adapt the arcolinux-nemesis scripts to customize your system further.
– Pamac or Octopi: These tools offer a straightforward way to search, install, or remove software with just a few clicks.


Entering the command “iso” in the terminal on ArcoLinux will display the version of the ISO utilized for the operating system’s installation.

However, this command will NOT inform you about the status of your system updates or verify their accuracy and completeness.

Monitoring and ensuring the update process is correctly completed remains your responsibility.

More detailed information can be found in the commits
On github.