diff options
| author | Craig Jennings <c@cjennings.net> | 2026-09-13 07:02:39 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-09-13 07:02:39 -0500 |
| commit | c667485437e9e34a2517c963152a1a86dbc19972 (patch) | |
| tree | 2881ceb0f527cd2f25395cd630629fa522da6f6f /dotfiles/common/documents | |
| parent | 38b1758716f5e5086eac9e9cdc0f0adfba9e54e5 (diff) | |
| download | archsetup-c667485437e9e34a2517c963152a1a86dbc19972.tar.gz archsetup-c667485437e9e34a2517c963152a1a86dbc19972.zip | |
docs(health-check): record the velox 2026-09-12 findings
These come from velox's 2026-09-12 health check. The Framework 04.02 BIOS update re-enabled Secure Boot, which rejects the unsigned ZFSBootMenu loader and reads as "no bootable device" while the boot entries are intact. I added a pre-firmware-update checklist to Phase 3 and a check-Secure-Boot-first section to the velox boot-entry reference.
Four Known Issues entries cover the Secure Boot flip, fwupdmgr activating passim, the topgrade containers step failing on local images and the harmless mkinitcpio firmware warnings. Phase 3 also notes why lsinitcpio needs sudo: the images are 0600, so an unprivileged run errors on stderr with an empty stdout, and a piped count reads 0.
Diffstat (limited to 'dotfiles/common/documents')
0 files changed, 0 insertions, 0 deletions