Skip to content

Real hardware

From QEMU to a 2012 laptop

On 10 October 2026 AriCodeOS booted on physical hardware for the first time: an Intel 7 series laptop, booting from a USB stick, without ever touching the internal disk.

The first boot

Eleven photos of a screen

With no serial port on the laptop, the screen was the only diagnostic channel. Each photo narrowed the problem down; each fix became a test scenario or an architecture decision.

Photo 1

Stuck on the slots line

AriBoot verified slot A and the screen froze. Opening the framebuffer exclusively had disconnected the firmware console, so every later trace was invisible. Fix: non-exclusive GOP, memory traces and boot beacons.

Photos 2–3

A hang in GetMemoryMap

With the traces visible, the hang was in the first GetMemoryMap call, right after reserving pages with a custom memory type. ADR 0021: reserve only standard types; BootInfo v4.

Photo 4

First complete boot

Kernel, PCI, init and ARICODEOS_KERNEL_READY on real hardware.

ADR 0022

A USB controller without MSI-X

The laptop's xHCI only offers MSI, so the driver framework gained MSI alongside MSI-X.

Photo 6

xHCI ready, no devices

On these Intel machines the ports start on the EHCI controllers. ADR 0023: usbd routes them to the xHCI, asks the firmware for the handoff and serves the USB stick as a block device.

Photo 7

A stick that refuses to flush

The USB stick was read, but it rejected SYNCHRONIZE CACHE. The command is now optional.

Photo 8

An interactive shell

The AriCodeOS shell on the laptop, with AriFS on the USB stick and the PS/2 keyboard. Backspace, cursor and history followed.

Photo 11

Wired networking

A shared network core and a Realtek r8169 driver: DHCP, ping to the router in 1 ms and DNS resolution.

Version 0.10

Reachable and updatable over the network

SSH into the laptop, HTTPS to real sites, and versions 2 to 5 of the system downloaded and installed without touching the USB stick.

Version 0.11

USB 2.0 and a signed update index

Both EHCI controllers ready at every boot, versions 2 to 6 installed from a signed index, and the laptop reinstalled from a stick signed with the release key.

Version 0.12

The audit of 0.11, verified on the laptop

Version 8 from a production-signed index: storage, network, HTTPS and the new diag lines, with no fault event at boot.

Version 0.13

DMA lifetime, verified on the laptop

Versions 9 and 10 over the network: every driver turns bus mastering on itself after resetting its device, the firmware USB handoff still works, and no fault event.

Version 0.14

Updates from GitHub

Downloads from the project’s GitHub releases through both redirects over TLS, development builds through their own channel, run bench over SSH and a seed carried across boots.

Version 0.15

The failure-pattern review, on the laptop

Development build 12: network, USB keyboard and storage, SSH with an unchanged host key, and HTTPS to GitHub and Google.

Version 0.17

Ten times faster SSH

Development build 19: SSH output from 0.12 to 1.15 MB/s on the same network after rebuilding TCP’s transmission, and HTTPS to GitHub, Google and this website through rustls.

Version 0.18

The desktop on the laptop

The desktop stick boots into the launcher with the laptop’s PS/2 keyboard and touchpad. Testing it there found the trailing pointer, the missing accents and windows that could not be closed, all fixed before the release.

Version 0.19

The panel and the GPU

The kernel gives the panel its own 1366×768 instead of the firmware’s 800×600, drives the HD 4000’s engine and runs compute on its EUs; on the same Core i3-3217U, an empty system call takes 260 ns.

The machine

The reference laptop

  • Intel 7 series laptop from 2012, UEFI firmware
  • xHCI 8086:1e31 plus two EHCI controllers
  • Realtek 10ec:8136 Ethernet — supported
  • Atheros AR9485 Wi-Fi — not supported
  • Built-in PS/2 keyboard as the kernel console
  • No DMAR table, so the IOMMU stays off on this machine

Try it

Boot it from a USB stick

AriCodeOS never writes to the internal disk: it boots from, and writes only to, its own USB stick. Even so, the stick is wiped completely. You need an x86-64 machine with UEFI (not CSM), Secure Boot disabled and a USB stick of at least 128 MiB. Download an image from the latest release, or build it from source: the base system with the text console, or the desktop stick, which boots into the desktop. For a Spanish keyboard, add kbd=es to aricodeos/cmdline.txt on the stick’s EFI partition. Once it has network, update and upgrade fetch new versions from GitHub; from 0.17 or earlier, go to 0.18.0 first, as the release notes explain. On a stick with AriFS v2, update profile add desktop installs the desktop’s applications.

Release 0.19.0
# base system; for the desktop, use aricodeos-0.19.0-desktop-usb.img.xz
curl -LO https://github.com/AriCodeLabs/AriCodeOS/releases/download/v0.19.0/aricodeos-0.19.0-usb.img.xz
curl -LO https://github.com/AriCodeLabs/AriCodeOS/releases/download/v0.19.0/SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
xz -d aricodeos-0.19.0-usb.img.xz
lsblk     # find the stick, NEVER the internal disk
sudo dd if=aricodeos-0.19.0-usb.img of=/dev/sdX bs=4M conv=fsync status=progress
Or build it from source
cargo xtask usb-image                            # build/aricodeos-usb.img
cargo xtask usb-image --cmdline "shell kbd=es"   # Spanish keyboard