CONTEXT: flashing moves to talos (SD reader not detected on straylight)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-04 15:01:47 -07:00
co-authored by Claude Sonnet 5.5
parent 4b5692f2b3
commit 3b2c6aaf4f
+5 -2
View File
@@ -18,8 +18,11 @@ enclosure, speakers. Work until those arrive is limited to what the Pi, HAT and
`b23371a5c8d02f612c26e7c18cacb81c5a48f968c7c66a2645391320aa94351e` (from
cdimage.ubuntu.com/releases/24.04/release/SHA256SUMS). It was downloaded to the session
scratchpad under `/tmp`, which a reboot likely cleared; re-download and re-verify.
- The Pi is not running yet. No card has been written. Dev host is NixOS (has `xz`, `dd`,
`udisksctl`; no `rpi-imager`).
- The Pi is not running yet. No card has been written. `straylight` (NixOS; has `xz`, `dd`,
`udisksctl`, no `rpi-imager`) never detected the Framework SD expansion card: no kernel event
in two bays, so the flashing moves to **`talos`**, where the owner confirmed the card mounts.
Continue the session there: clone the repo, read this file, re-download and re-verify the
image (the copy on straylight is in its `/tmp`). Check talos's OS and available tools first.
- **Open questions for the owner before flashing:** Wi-Fi credentials or Ethernet for first boot;
hostname (proposed `hermes-robot`); username; SSH key (default `~/.ssh/id_ed25519.pub`).
Plan: write the image after the owner confirms the device from `lsblk`, then edit cloud-init