bigbox1 (Ryzen 5 4600G, B550 GAMING X V2, BIOS FC) hard-froze 5 times in 16 days (Nov 4 19:07, Nov 16 01:22, Nov 17 02:03, Nov 17 22:59, Nov 19 18:20 ET), always while idle, each time with no log line and an "uncleanly shut down" journal on the next boot. That matches the known Ryzen deep-idle (C6) freeze. acpi_idle exposes C1 (MWAIT), C2 and C3 (lat 350us, the deep state); processor.max_cstate=1 keeps cores out of C2/C3. Cost: a few watts more at idle. The runtime watchdog (common.dns, SP5100 TCO, 30s) was armed during the Nov 19 boot and did not reset the box, so it is not a safety net here and is left as is.
5.4 KiB
5.4 KiB
hosts/
One folder per managed machine, plus hardware configs and host-specific scripts.
Structure
hosts/
├── <hostname>/ # Per-host folder (default.nix is the entry point)
│ ├── default.nix # Main config: skyg options, top-level settings
│ ├── packages.nix # environment.systemPackages (large hosts only)
│ ├── services.nix # Service configs (tailscale, ollama, steam, …)
│ ├── hardware.nix # Kernel params, GPU tuning, boot (large hosts only)
│ ├── networking.nix # Firewall, NFS mounts, DNS (large hosts only)
│ ├── containers.nix # Container service groups (hl-minipc1, hl-minipc2)
│ └── ... # Additional host-specific sub-files as needed
├── <hostname>.hardware-configuration.nix # Generated — DO NOT EDIT
├── <hostname>.disko.nix # Declarative disk layout (hl-fws1 only)
└── scripts/
├── fwbook/ # fwbook-specific shell scripts
│ ├── functions.sh # ZSH functions sourced at shell startup
│ └── functions.nu # NuShell helpers
├── fw1/
│ └── gs.sh # gamescope/Steam launch wrapper
└── hl-minipc1/
└── buzz-manage.sh # Buzz stack management CLI
Managed Hosts
| Folder | Host | Role |
|---|---|---|
fwbook/ |
fwbook | Framework 13 AMD — personal laptop / daily driver |
hl-fwdesk/ |
hl-fwdesk | Framework Desktop AI Max 300 — AI workstation; buildbot-nix CI worker (4 cores); nbot master |
hl-fws1/ |
hl-fws1 | Framework 11th Intel — K3s server node; nbot worker |
hl-bigbox1/ |
hl-bigbox1 | AI/compute server (NVIDIA + AMD); Immich machine-learning (CUDA); CPU idle capped at C1 (processor.max_cstate=1) against Ryzen idle freezes |
hl-bigbox2/ |
hl-bigbox2 | NFS storage server; Immich server/db (docker, immich.home.sosnovsky.ca) |
hl-minipc1/ |
hl-minipc1 | Core infra: Gitea (native or containerized), nix-serve, registry, Buzz (docker, buzz-manage CLI), monitoring (Grafana, Prometheus, Loki, OTel collector) |
hl-minipc2/ |
hl-minipc2 | Container/media server; Umami for LoopRail telemetry (own nspawn container, 10.0.101.14, reachable only from Caddy) |
hl-minipc3/ |
hl-minipc3 | K3s worker node; central Caddy reverse-proxy (*.home.sosnovsky.ca, plus gitea.skyg.ca HTTP/SSH); serves LoopRail docs at looprails.skyg.ca, plus its guarded telemetry route /t/v1 → Umami and the LAN-only umami.home.sosnovsky.ca; buildbot-nix CI master + worker (2 cores) |
hl-pi1/ |
hl-pi1 | Raspberry Pi CM4 (aarch64) — headless server, SSH only |
hl-pi2/ |
hl-pi2 | Raspberry Pi 4 (aarch64) — headless server, SSH only |
hl-terra1/ |
hl-terra1 | NFS storage + Jellyfin backup |
iso/ |
iso | Bootable NixOS installer image |
Rules
- Do not add
imports = [...]to host files — module composition happens inflake.nixviamodules/main.nix - Do not edit
*.hardware-configuration.nix— these are generated and will be overwritten - Hosts with a
<hostname>.disko.nixown theirfileSystemsvia disko; if a generatedhardware-configuration.nixstill contains its ownfileSystemsstanzas for the same host, that's a conflict the machine's owner needs to resolve by hand (regenerating or trimming it) — not something to script around - Host-specific packages and one-off settings belong here; anything reused across hosts belongs in
modules/ - See
docs/hosts/README.mdfor full per-host service/port/package reference
Rules
- Do not add
imports = [...]to host files — module composition happens inflake.nixviamodules/main.nix - Do not edit
*.hardware-configuration.nix— these are generated and will be overwritten - Hosts with a
<hostname>.disko.nixown theirfileSystemsvia disko; if a generatedhardware-configuration.nixstill contains its ownfileSystemsstanzas for the same host, that's a conflict the machine's owner needs to resolve by hand (regenerating or trimming it) — not something to script around - Host-specific packages and one-off settings belong here; anything reused across hosts belongs in
modules/ - See
docs/hosts/README.mdfor full per-host service/port/package reference