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 | 28d576db056d35033061a2db41b7a7ac5ac6a64e (patch) | |
| tree | 41d1e6e79c6eda8ff66e798105ef3adaac67d082 /todo.org | |
| parent | 495d16d17b49d37336f1c1189543928b396449e0 (diff) | |
| download | archsetup-28d576db056d35033061a2db41b7a7ac5ac6a64e.tar.gz archsetup-28d576db056d35033061a2db41b7a7ac5ac6a64e.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 'todo.org')
0 files changed, 0 insertions, 0 deletions