Reviving a 32-Bit Asus Eee PC 1000HE with Arch Linux 32
A technical breakdown details the deployment of Arch Linux 32 on a legacy netbook limited by an Intel Atom N280 processor and 1GB of DDR2 RAM. The installation process highlights legacy BIOS firmware anomalies, 32-bit network stack configuration, and storage partitioning strategies for memory-constrained hardware.
Target Hardware and OS Selection
The ASUS Eee PC 1000HE, originally released in 2009, is built around an Intel Atom N280 processor and 1GB of DDR2 RAM. The N280 operates at a clock speed of 1.667 GHz, equipped with 56KB of L1 cache and 512KB of L2 cache. Because this architecture is strictly 32-bit, and official x86 support was deprecated by upstream Arch Linux in 2017, the deployment required the community-maintained Arch Linux 32 fork.
To ensure minimal system overhead, the installation was conducted via the CLI to construct a highly tailored environment from the ground up. The installation media (`archlinux32-2023.03.02-i686.iso`) was verified via GPG against its signature file:
```bash gpg --keyserver-options auto-key-retrieve --verify archlinux32-2023.03.02-i686.iso.sig ```
Once validated, the image was written to a USB drive using Rufus on a Windows desktop, and the target netbook was configured via BIOS to prioritize the USB device for booting.
Network Association and Time Synchronization
The Arch Linux installation image boots into a `zsh` environment. Establishing a network connection is required to retrieve packages during bootstrap.
- `lo`: The virtual loopback interface.
- `enp3s0`: The physical Ethernet interface residing on PCI bus 3, slot 0.
- `wlan0`: The wireless LAN interface.
Because the netbook's integrated wireless card does not support 5GHz bands, connection to a 2.4GHz access point was required. The `iwd` client (`iwctl`) was used to scan for available networks and authenticate:
```bash
iwctl
station wlan0 scan
station wlan0 get-networks
station wlan0 connect
Connectivity was verified via ICMP ping to `archlinux32.org`. System time was synchronized to prevent TLS handshake failures during package retrieval by enabling Network Time Protocol (NTP) via `timedatectl`:
```bash timedatectl set-ntp true ```
Storage Partitioning and Firmware Workarounds
The internal storage device is a 150GB mechanical hard drive (`/dev/sdb`, specifically model ST9160410AS). Analysis of the preexisting disk layout revealed an EFI partition. On this specific legacy BIOS motherboard, this partition was not utilized for native UEFI booting; instead, it supported the BIOS "Boot Booster" feature. This feature speeds up boot times by caching Power-On Self Test (POST) hardware initialization data directly in this dedicated partition.
The disk was repartitioned using `fdisk` using an MBR partition scheme. The structural layout was defined as:
- `/dev/sdb1`: Type 82 (Linux Swap)
- `/dev/sdb2`: Type 83 (Linux Native, bootable flag set)
For a machine limited to 1GB of physical RAM, swap space configuration is critical. Setting an insufficient swap allocation risks encountering out-of-memory (OOM) conditions or "No space left on device" errors during standard system updates or memory-intensive tasks.