Skip to content

Instantly share code, notes, and snippets.

@yorickdowne
yorickdowne / friday.md
Last active August 7, 2025 09:10
Debian 13 trixie upgrade

Debian 13

This is a placeholder for instructions when Debian 13 is released on the 9th of August 2025

To start, read the official release notes.

If your install fits into "vanilla Debian plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Debian 13 "trixie" from Debian 12 "bookworm" can be helpful. 3rd-party repos are handled with a find command.

Note upgrade is only supported from Debian 12 to Debian 13. If you are on Debian 11, upgrade to Debian 12 first. Then once on Debian 12, you can upgrade to Debian 13.

@yorickdowne
yorickdowne / jammy.md
Last active February 26, 2025 15:31
Upgrade to Ubuntu Jammy Jellyfish

Ubuntu Jammy Jellyfish

To start, read the official release notes.

If your install fits into "vanilla Ubuntu plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Ubuntu 22.04 "Jammy Jellyfish" from Ubuntu 20.04 "Focal Fossa" can be helpful. 3rd-party repos are handled with a find command.

Some Intel NUC10/11 with I225-LM or I225-V Ethernet chip may cause "freezing" of the OS after this update, if wired Ethernet is in use. There are some reports that a BIOS update plus using the hwe kernel can resolve that.

@yorickdowne
yorickdowne / tremor.md
Last active July 16, 2025 09:07
Stabilize an Asus or Intel NUC for 24/7 server operations

The issue

Asus (formerly Intel) NUCs weren't designed for use as a 24/7 server, though they see enthusiastic use as such. Some users report instability. And while some of that can be bad RAM or a faulty motherboard / CPU, some can also just be configuration issues. And some is plain heat.

It's a little tough to nail it down. Here are some good practices to follow, to have a stable NUC.

BIOS update

@yorickdowne
yorickdowne / supergau.md
Last active March 10, 2025 19:28
Holesky Pectra recovery

Holesky has been recovered

As of 2024-03-10 19:30 UTC, Holesky finalized on the correct chain. You can use recent versions of your clients and sync normally.

Historical content below, no longer relevant

Recover Eth Docker Holesky setup

You need:

  • 64 GiB of RAM, or 32 GiB + 32 GiB swap. 16 GiB is unlikely to work