chore(eod): pre-reboot cleanup and documentation update
- Add scripts/update-cli-suite.sh for Manjaro/Arch CLI tool maintenance - Update .gitignore: add logs/ and docs/tech/capabilities/ exclusions - Update CHANGELOG.md with 2026-04-02 NVMe benchmark + firmware work - Update NEXT_STEPS.md: post-reboot verification tasks for GXA7801Q
This commit is contained in:
@@ -1,13 +1,35 @@
|
||||
# Next Steps - 2026-03-17
|
||||
# Next Steps - 2026-04-02
|
||||
|
||||
## High Priority
|
||||
## Immediate (Post-Reboot - GXA7801Q Firmware Activation)
|
||||
|
||||
> NVMe firmware GXA7801Q was applied 2026-04-02 but requires reboot to activate.
|
||||
> Run `sudo reboot` when ready.
|
||||
|
||||
- [ ] Reboot workstation to activate NVMe firmware GXA7801Q
|
||||
- [ ] Verify firmware: `nvme list` should show `GXA7801Q` (was `GXA7401Q`)
|
||||
- [ ] Check SMART health post-update: `sudo nvme smart-log /dev/nvme0n1`
|
||||
- [ ] Run post-update fio benchmark (same parameters as pre-update):
|
||||
```bash
|
||||
fio --directory=/tmp --name=seq-read --rw=read --bs=4k --iodepth=32 \
|
||||
--ioengine=libaio --direct=1 --size=1g --runtime=30 --time_based
|
||||
```
|
||||
- [ ] Document before/after comparison in `docs/tech/nvme-benchmark-post-gxa7801q.md`
|
||||
- [ ] Update `docs/tech/firmware-update-research.md` status from "reboot pending" to "complete"
|
||||
|
||||
## Short Term
|
||||
|
||||
- [ ] Update `linux-firmware` and kernel packages: `sudo pacman -Syu linux-firmware`
|
||||
- [ ] Check NVIDIA driver version: `pacman -Q nvidia`
|
||||
- [ ] Run `scripts/update-cli-suite.sh` to sync CLI tool suite
|
||||
- [ ] Monitor system behavior under multi-day sustained load to ensure `zswap` and `MGLRU` keep the system responsive.
|
||||
- [ ] Verify that `archlinux-keyring-wkd-sync.service` failure is resolved or investigate further (currently noted in health report).
|
||||
- [ ] Verify that `archlinux-keyring-wkd-sync.service` failure is resolved or investigate further.
|
||||
|
||||
## Optimization
|
||||
|
||||
- [ ] Evaluate if `systemd-oomd` is aggressive enough for interactive desktop use; if not, consider testing `earlyoom` as an alternative.
|
||||
- [ ] Automate periodic S.M.A.R.T. checks via a systemd timer (currently manual).
|
||||
|
||||
## Infrastructure
|
||||
|
||||
- [ ] Consolidate Ansible variables for Docker memory limits into `ansible/vars/main.yml`.
|
||||
- [ ] Extend `scripts/maintenance.sh` to include a summary of the last 24h OOM events (if any).
|
||||
|
||||
Reference in New Issue
Block a user