A simple, lightweight distribution for 32-bit CPUs

You've reached the website for Arch Linux 32, the community maintained continuation of 32-bit support for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple.

Currently we have official packages optimized for the i686 and pentium4 architectures. Also most(ly) non-graphical packages are available for i486, too. Have a look at the required cpu flags to decide which architecture is the right one for you. Most packages from Arch Linux's community-operated package repository are also compatible with Arch Linux 32.

Installation media which boot on i686 can be found here.

Join us on #archlinux32 IRC channel on Libera, check out our forums or subscribe to the mailing list to get your feet wet. Also glance through the Arch Wiki if you want to learn more about upstream Arch.

Latest News

RSS Feed RSS Feed

Bugtracker migration to GitLab completed


We are happy to announce that the migration of the bugtracker to GitLab is done! 🥳

Thanks to everyone who has helped during the migration!

This means the issue tracker and merge requests on the GitLab package repos are now enabled.

The old bugtracker will subsequently be closed down. For archiving reasons there will be a static copy so that links (for example the randomly picked Task #56716) are still stable, migrated bugs have a closing comment pointing to the new URL on GitLab.

Packaging bugs are now opened on the repo hosting the corresponding packaging sources, the "Add a new Bug" button on the package page on archlinux.org will automatically direct you to the correct place to open the issue. The workflow afterwards is mostly the same, first our Bug Wranglers will have a look at the issues and triage them, and then they will be handed over to the respective Package Maintainers to fix. A list of all issues can be found here.

If you do not have an account for GitLab already (which authenticates against our SSO service), please write us a mail with your desired username to accountsupport@archlinux.org as advised in the banner.

Incoming changes in JDK / JRE 21 packages may require manual intervention


We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21.

To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work.

This will (potentially) require a manual user action during upgrade:

  • If you have both JDK and JRE installed you can manually install the JDK with pacman -Sy jdk-openjdk && pacman -Su and this removes the JRE related packages.
  • If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
  • If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.

At the moment this is only valid for the upcoming JDK 21 release.

Changes to default password hashing algorithm and umask settings


With shadow >= 4.14.0, Arch Linux's default password hashing algorithm changed from SHA512 to yescrypt.

Furthermore, the umask settings are now configured in /etc/login.defs instead of /etc/profile.

This should not require any manual intervention.

Reasons for Yescrypt

The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam) and its stronger resilience towards password cracking attempts over SHA512.

Although the winner of the Password Hashing Competition has been argon2, this algorithm is not yet available in libxcrypt (attempt one, attempt two).

Configuring yescrypt

The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix module (i.e. in /etc/pam.d/system-auth).

General list of changes

  • yescrypt is used as default password hashing algorithm, instead of SHA512
  • pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
  • changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile

ansible-core >= 2.15.3-1 update may require manual intervention


As of ansible-core 2.15.3, upstream moved documentation and examples to a separate dedicated repository (see the related changelogs).
This means that, starting from version 2.15.3 the ansible-core package will stop shipping documentation and a default configuration example under /etc/ansible/ansible.cfg.

Regarding the documentation, it is available online: https://docs.ansible.com/
As for the configuration file, as explained in the wiki, a base config can be generated with the following command:

ansible-config init --disabled > ansible.cfg

After updating from ansible-core <= 2.15.2-1 to >= 2.15.3-1, everyone using a custom global Ansible configuration file stored under /etc/ansible/ansible.cfg will have their configuration saved as a pacsave file.
To restore it, run the following command:

mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg

Older News

budgie-desktop >= 10.7.2-6 update requires manual intervention
Shim packages required for 'icu'
New package signing keys
TeX Live package reorganization
OpenBLAS >= 0.3.23-2 update requires manual intervention
Git Migration
Git migration completed
upstream git migration
Git migration announcement
In case of key problems
Dropping Haskell
Switch to the base-devel meta package requires manual intervention
OpenSSL 3.0.7
systemd 251.2 breaks logins
CA certificates file is empty
ISO 2022.02.01 available
nss 3.73 crashes firefox
error while loading shared libraries: libicui18n.so.68
Warning about upgrading to zstd 1.5.1
libffi.so.7: cannot open shared object file: No such file or directory
pacman upgrade brings pentium4 automatically for via processors

Recent Updates (more)

RSS Feed
libvdpau 1.5-2.0 i686
dns-over-https 2.3.4-1.0 i686
go-md2man 2.0.3-1.0 i686
fuse-overlayfs 1.13-1.0 i686
ethtool 1:6.5-1.0 i686
apache 2.4.58-1.0 i686
poke 3.3-1.0 i686
python-typed-ast 1.5.5-1.0 i686
fio 3.36-1.0 i686
raft 0.18.0-1.0 i686
dqlite 1.16.0-1.0 i686
shairport-sync 4.3.2-1.0 i686
git-lfs 3.4.0-1.0 i686
step-ca 0.25.0-1.0 i686
vim-editorconfig 1.2.0-1.0 i686