Skip to content
Open WebUI to FastFlowLM to the XDNA2 NPU on IPv6 loopback: 21 W answering, 232,000 tokens in one prompt, three years from AMD's keynote to Linux

Running An LLM On The Ryzen AI NPU, In A Container

The NPU in a Ryzen AI laptop is 50 TOPS that sits idle on most Linux installs. This walks through building AMD’s amdxdna driver and keeping only the kernel module on the host, building FastFlowLM with AMD’s XRT runtime into a rootless podman container matched to that driver, binding everything to IPv6 loopback and starting it at boot with Quadlet. Then what it does: nine models benchmarked, a 232,000-token context test, Whisper speech-to-text at ten times real time, Open WebUI and the 7,000 hidden tokens it was adding to every message, and the speed and energy of the NPU measured against llama.cpp on the Radeon 860M iGPU. Last, the timeline: three years from AMD announcing Ryzen AI to a language model on its NPU under Linux, delivered by a project AMD did not start, while the effort went to Copilot+ on the Fisher-Price OS (Windows) instead of the data centre and the Linux tooling AI professionals actually use.

13th November 2026 · 24 min · 5853 words · Damien Dye

Sorting TSC When Your Firmware Is Broken

On every boot for four months my ThinkPad E595 handed Linux one CPU core three seconds behind the other seven, and the kernel dropped the TSC for HPET. What the warning means, why an AMD Zen machine has no way to repair it from inside Linux, what 40 boots of journal say about the firmware, why tsc=reliable is the wrong answer, and how tscsync measures and moves the counters in UEFI before the kernel ever sees them, including the one core it marked BAD that Linux accepted anyway. Updated for BIOS 1.30: it does not fix the offset, and the kernel’s clocksource watchdog dropped the TSC on two boots even after tscsync synced the cores. With tsc=nowatchdog it held, and a five-minute check against the real-time clock, source included, found no warps and no drift. Last, what the fallback does on any KVM hypervisor, Proxmox or not: the master clock goes, guests lose their fast clock read, and on this laptop a guest clock read came out seven times slower.

11th October 2026 · 23 min · 5100 words · Damien Dye

My YubiKey Logs Me In. My Keyring Never Got Told.

Log in with a YubiKey and GNOME asks for a password anyway, because the login keyring is encrypted with a password your login never produced. This post covers why pam_u2f being sufficient starves the keyring, what the usual fixes cost (blank password, typing it anyway, the TPM), and the fix I built: the key’s FIDO2 hmac-secret, gated on PIN and touch, decrypting a stored copy of the account password and unlocking oo7-daemon at login. Then what the build turned up: Fedora 45 had swapped gnome-keyring for oo7, oo7’s placeholder keyring takes the first password you type as its own, the FIDO2 tools only read a PIN from a terminal, and a reset script that would have left me with no keyring at all, caught by testing it against a throwaway daemon first. The scripts, an installer and that test harness are available to download.

7th October 2026 · 12 min · 2567 words · Damien Dye
A name lookup passing through systemd-resolved's stub listener into a cache, a validator and an encrypted transport, with the validator and the encryption switched off

Resolved: The Resolver You Are Already Running

systemd-resolved is running on most Linux desktops right now, caching every lookup and validating none of them. This walks the resolution path from nss-resolve to the two stub listeners, measures what the cache is worth on a real machine, turns DNSSEC on and shows the three verdicts it can return, and explains why validation is off by default when upstream ships it on. Then a census of how little of the web is actually signed, DNS over TLS and its strict-versus-opportunistic trap, and the DNS over HTTPS support that has been requested since 2018 and still does not exist. Ends with what Fedora, Ubuntu, Debian and the RHEL family each ship, how to wire it into each one, and why the features your distro disabled are defaults rather than missing code.

27th September 2026 · 38 min · 8443 words · Damien Dye

Webex Is Looking For Your Certificates On A Cisco Build Server

Webex 46.8.0.35631 on Fedora 44 sits behind a yellow banner reading “Offline - No internet connection” while every other program on the machine reaches the internet without complaint. It stopped the VoIP line dead. The network was never the problem: Cisco bundle their own fork of OpenSSL and built it with OPENSSLDIR set to /workspace/.conan2/p/b/cisco8ee8b59cf93de/p/ssl, a directory that exists on a build container and nowhere else, so it loads no trust anchors and every handshake fails. The post runs in order: what the broken state actually is, asking the shipped library where it thinks its certificates live, reproducing the exact error code outside Webex, why nothing warns you, the two fixes that do not work and why, and the one that does. Then the build process: they used $ORIGIN for the code and left three data paths absolute, the RPM header names a container ID so the container was already in the pipeline and never used to run the result, the package requires a glibc from 2018 because they will not link statically, 2.2 GB is shipped twice, and it carries no documentation and no file marked as configuration. Then how it should have been built, the six fixes and the one-line check that catches it. And finally the cross-check: Cisco hold 98 entries in CISA’s known-exploited catalogue, second only to Microsoft, and a trust path nobody checked and a bypass nobody checked are the same failure at different stakes.

15th September 2026 · 42 min · 9141 words · Damien Dye