From 3472deda0fcc13425717554b3708052b078ff9d2 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Mon, 5 Oct 2026 22:33:45 -0600 Subject: chore(assets): file the nine inbox handoffs worth keeping The inbox held 74 processed handoffs from July and August. Nine carry reference material (three hardware photos, the board-swap context and the settings-panel and agenda-json notes) and move flat into assets/ under dated names. The photos are downscaled to 1600px and stripped of EXIF before entering a cloneable repo. Four more were already filed under docs/design on 09-13, so the archive's diagnosis link now points there. Two stay out of the tree on purpose: their facts are recorded elsewhere and their text is not for a public repo. I deleted the rest: acknowledgements, receipts and requests that had already become tasks. --- assets/2026-08-13-velox-amd-board-swap-context.org | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 assets/2026-08-13-velox-amd-board-swap-context.org (limited to 'assets/2026-08-13-velox-amd-board-swap-context.org') diff --git a/assets/2026-08-13-velox-amd-board-swap-context.org b/assets/2026-08-13-velox-amd-board-swap-context.org new file mode 100644 index 0000000..531c365 --- /dev/null +++ b/assets/2026-08-13-velox-amd-board-swap-context.org @@ -0,0 +1,5 @@ +#+TITLE: Velox context for the microcode check and possible reinstall +#+SOURCE: from work +#+DATE: 2026-08-13 14:34:48 -0500 + +Velox context for the microcode check and possible reinstall. Velox's mainboard was swapped today from Intel to AMD (Ryzen AI 9 HX 370, Radeon 890M, 96GB new RAM, trained fine). The old SSD is intact but the new board's NVRAM is empty, so there is no boot entry: the fix in progress from the work session is boot the Arch USB (Secure Boot enforcement must be disabled first, factory default is on), chroot, efibootmgr --create --disk /dev/nvme0n1 --part 1 --label GRUB --loader '\EFI\GRUB\grubx64.efi', then swap intel-ucode for amd-ucode, grub-mkconfig, mkinitcpio -P. Craig may instead do a full reinstall via archsetup. The ask he is bringing to this session: verify archsetup installs the correct microcode on AMD — whether it hardcodes intel-ucode or detects the CPU vendor — and fix it if it is Intel-only, since velox is now AMD and flies with him Sunday. Also note: the new board reset the RTC to 2025-01-01, so first boot may hit TLS/pacman signature grumpiness until the clock syncs. -- cgit v1.2.3