Breathing New Life into a 15-Year-Old Netbook via Arch Linux

By 박성범 (Simon Park)
Date: 2026.07.04 | Language: KO | EN

💻 The Hardware Legacy

I still possess a netbook purchased back in 2009: the ASUS Eee PC 1000HE. To put its capabilities into perspective, let's look at the internals. It is powered by an Intel Atom N280 processor paired with 1GB of DDR2 RAM.

The Atom N-series was Intel's answer for the budget market—low-cost, low-power, and low-performance. To understand just how limited this machine is, we can compare its specs to a modern budget chip.

CPU Comparison: Then vs. Now

Feature	Intel Atom N280 (2009)	Intel Core i3 N305 (2023)
Clock Speed	$1.667\text{ GHz}$	$3.8\text{ GHz}$
L1 Cache	$56\text{ KB}$	$768\text{ KB}$
L2 Cache	$512\text{ KB}$	$4\text{ MB}$

These specifications were the inherent trade-offs of the "netbook" era. While it was never meant to compete with full-sized laptops, it sufficed for basic web surfing and word processing in its prime.

However, by 2012, the tide turned. As websites became more interactive and software grew more bloated, the aging HDD and meager CPU made routine tasks a struggle.

🔄 Seeking a New Operating System

In 2023, I rediscovered this machine in storage. Upon booting, I was greeted by the nostalgic, yet tacky, Windows XP interface. The performance was abysmal; opening Windows Explorer took several seconds, and the cursor would stutter incessantly.

I wondered: Was it always this slow, or had my perception of "fast" simply evolved?

Regardless, I wanted to repurpose it as a basic server or a dedicated YouTube machine. This required a total OS overhaul.

The Selection Process

I evaluated several options based on the strict $1\text{GB}$ RAM limit:

~~Windows XP~~: End-of-life since 2014; insecure.
~~Windows 7/10/11~~: Too resource-heavy for $1\text{GB}$ of RAM.
~~Ubuntu~~: While it technically supports $512\text{MB}$ , my past experience showed it felt sluggish on low-end hardware.

I needed something minimalist, modular, and extremely lightweight. This led me to Arch Linux, a distribution centered on simplicity and user-centricity. It offered the perfect opportunity to build a custom environment from scratch and learn more about OS internals before the new semester.

🛠️ Before Installation

Because the Atom N2xx series only supports 32-bit architecture, and official Arch Linux dropped x86 support after 2017, I had to use Arch Linux 32, a community-maintained fork.

Pre-Flight Checklist

Preparing the Boot Media

First, I verified the image to ensure it hadn't been tampered with using the gpg command:

$ gpg --keyserver-options auto-key-retrieve --verify archlinux32-2023.03.02-i686.iso.sig

Once verified, I used Rufus on a separate Windows machine to flash the ISO onto a USB drive. I then inserted the drive into the Eee PC, entered the BIOS, and prioritized the USB drive as the primary boot device.

🌐 Connecting to the Internet

The installation environment boots into the zsh shell. Since Arch is installed via the internet, connectivity is the first priority.

Running ip link reveals the available interfaces:

lo: The loopback interface (virtual, used for the system to talk to itself via 127.0.0.1).
enp3s0: The Ethernet port (PCI bus 3, slot 0).
wlan0: The Wireless adapter.

To ensure the Wi-Fi wasn't disabled by a hardware or software switch, I used rfkill:

$ rfkill
ID TYPE DEVICE            SOFT HARD
0  wlan eeepc-wlan        unblocked unblocked
1  bluetooth eeepc-bluetooth unblocked unblocked
2  wwan eeepc-wwan3g      unblocked unblocked

Since I preferred Wi-Fi, I utilized iwctl, the client for the iNet wireless daemon (iwd) developed by Intel.

The Connection Sequence:

$ iwctl
[iwctl]# device list
Devices -----------------------------------------------------------
Name Address Powered Adapter Mode 
-----------------------------------------------------------
wlan0 xx:xx:xx:xx:xx:xx on phy0 station

[iwctl]# station wlan0 scan
[iwctl]# station wlan0 get-networks
Available networks ----------------------------------
Network name Security Signal 
----------------------------------------------------
iptime psk **