TinyComputers.io

Latest Hardware Reviews

FreeBSD on a 2011 MacBook Pro: Fifteen Years of Progress, and Per Core It's a Tie

 · 18 min read

I put a 2011 MacBook Pro running FreeBSD 15.1 through the same Rust compile benchmark as my single-board computer fleet. It lands sixth of nine at 131.00s - behind a Raspberry Pi 5, ahead of a Banana Pi CM5-Pro. But normalized per core and per gigahertz, a 2011 Sandy Bridge core and a 2023 Cortex-A76 do the same amount of work to within 0.3%. Also: why SHA-256 is 5.7x slower here, how the ZFS ARC nearly sold me a 2.86 GB/s hard drive, and two benchmark results I threw out.
Recent
Programming Languages, Software Architecture The Config Language That Was Already There: A Ballistics REPL Written in Lattice  · 18 min read Software The Bullet Doesn't Go Where You Point It  · 8 min read Hardware Reviews FriendlyElec NanoPC-T6N Review: The Fastest Board on My Bench, and the Benchmark That Outgrew Itself  · 28 min read Operating Systems Four Partitions and a Borrowed Bootloader: NetBSD on the Milk-V Mars  · 17 min read

Sponsors

More Articles

Hardware Reviews

Banana Pi BPI-R4 Pro Review: A 10-Gigabit Router Board I Put to Work as a Bastion

 · 21 min read

Hands-on review of the Banana Pi BPI-R4 Pro, a MediaTek MT7988A (Filogic 880) router board with quad Cortex-A73, dual 10GbE, and 8GB RAM running OpenWRT. Benchmarked for what a router actually does - CoreMark 9533/37952, ~1 GB/s hardware AES, GbE line-rate networking, 50C under load - and deployed as a real SSH bastion and nginx reverse proxy. A different animal from a compute SBC, reviewed as one.
Infrastructure

Nothing Was Using the Cores: Three Idle Arm64 Boards, One HA k3s Cluster, and a BSD Build Farm

 · 18 min read

I had three small Arm64 boards on a shelf, each doing one modest thing and idling the rest of the time — an Orange Pi 5 Max running an occasional local LLM, two Raspberry Pi–class machines mostly serving a web page. Between them they had sixteen cores, forty gigabytes of RAM, and four terabytes of NVMe, and almost none of it was doing anything at any given moment. This is the story of resisting the urge to buy two more boards into a memory shortage, and instead turning that idle majority into a real three-node HA k3s cluster with embedded etcd, then teaching it to do the job the boxes had quietly been built for all along — compiling native FreeBSD, OpenBSD, and NetBSD Arm64 binaries — and the small pile of gotchas that stood between "three SBCs" and "a build farm," from a big.LITTLE crash loop to golden images that turned out to be live disks. And then everything else the reclaimed capacity paid for.
Operating Systems

The Driver Nobody Wrote: OpenBSD's ena(4) Works Now — and Can't Go Upstream

 · 17 min read

Five weeks ago I ended a post about writing OpenBSD's missing ena(4) driver with a confession disguised as a list — every way the thing didn't work yet. This is the post where I cross them all off. The driver does a full disk install now, comes up multiuser with the AWS network card as its only interface, lets me SSH in over it, pushes 3.16 Gbit across multiple queues with receive-side scaling, and runs unchanged on OpenBSD-current. It is, by every technical measure I set for myself, done. And that is exactly when it walked into the one wall effort can't move: code an AI wrote has no human author, so it cannot go into OpenBSD's tree — not for lack of quality, but for lack of a person. This is the story of finishing it, the one bug I never cracked, and what it means to write working systems code that, in the eyes of the thing it was written for, nobody wrote.
Operating Systems

The Doorbell That Killed the Device: Writing OpenBSD's Missing ena(4) Driver

 · 18 min read

A weeks ago I wrote about getting native OpenBSD/arm64 builds on Graviton by refusing to let OpenBSD touch AWS's network card at all — running it as a QEMU guest behind a virtio shim, because OpenBSD has no driver for Amazon's ENA adapter. This is the other half of that itch: actually writing the driver. It's the story of getting ena(4) to attach, watching the device kill itself a few microseconds after every bring-up, chasing five increasingly exotic theories for why, and finding that the real cause was the most boring thing imaginable — I initialized a queue in the wrong order. Plus the part nobody writes down: what "working" actually means, and exactly how far from "done" that still is.
Operating Systems

The OS That Couldn't See the Network: Native OpenBSD/arm64 Builds on AWS Graviton Metal

 · 17 min read

I wanted native OpenBSD/arm64 binaries for a project that ships them, and assumed the answer was a Graviton instance. It isn't — OpenBSD's arm64 kernel has no driver for AWS's network card, so the instance boots into a void you can never reach. This is the story of getting there anyway: by refusing to let OpenBSD touch the cloud's hardware at all, running it as a KVM guest inside QEMU on a bare-metal Graviton host, and the two device-tree gotchas, the serial-console install I handed to an AI agent, and a last-mile build failure I confidently blamed on the wrong thing.
Networking

The Tunnel Was the Easy Part: Site-to-Site WireGuard Between My House and a VPC

 · 14 min read

I wanted to close a database's public port and reach it from my house as if the VPC were just another room. WireGuard did that in fifteen minutes. The other day and a half went to an IP-address collision I'd created years earlier, a load-balancing router quietly breaking the tunnel's return path, and the slow lesson that a VPN doesn't connect two networks — it makes you confront every assumption each made while pretending the other didn't exist.

Topics

Retro Computing AI & Inference Hardware Projects Philosophy Economics Systems Programming

Reading Series

8+ posts Jevons Paradox & AI Economics What happens when cognitive output gets cheaper. Demand expansion, the biological ceiling, and the AI vampire. 3 parts Heidegger & Technology Enframing, standing reserve, and what happens when AI treats specifications as raw material for code generation. 8+ posts Z80 RetroShield Running a real Z80 on modern hardware. CP/M, Forth, Zork, custom PCBs, and a dual-processor design. 3 parts Sampo CPU & Compilers A custom RISC CPU from ISA design through FPGA implementation to an LLVM backend. 6 posts Tesla P40 Home Lab Four eBay GPUs, 96GB of VRAM, and every workload we can throw at them. LLMs, TTS, video generation. 3 parts The Lattice Language A programming language where mutability is a phase transition. Novel type system, bytecode VM, 100 opcodes.
View All Articles →
Written by Alex Jokela Software engineer by trade, tinkerer by nature, single-board computer hoarder by choice. More about me →