From b6aee456e80fd125f4f4aed016c15c150d3d5c6c Mon Sep 17 00:00:00 2001 From: Noah Date: Thu, 3 Sep 2026 19:18:08 -0600 Subject: [PATCH] Note where the VM's kernel is ahead of the panels The VM builds warden_defconfig plus virt.fragment, so it has CONFIG_BRIDGE; the vendor 5.10 kernel most panels still run does not. A Client-mode access point is bridged to the wired uplink and needs that, so the Wi-Fi page offers it here and declines on a 5.10 panel. Both answers are correct for the kernel underneath, which is exactly why it is worth writing down: a screenshot from the VM is not evidence about that page on a 5.10 panel until the fleet has moved to the 6.18 build. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01T2D2KtdgwbhbF6Mo64eUrn --- qemu/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/qemu/README.md b/qemu/README.md index 23607bf..065adbe 100644 --- a/qemu/README.md +++ b/qemu/README.md @@ -37,6 +37,15 @@ Documented guest deviations from production, set by stage-2 init: `WARDEN_HPMCU=0` (no mailbox SRAM on virt; flared >= flare-edge#106 fix required, or the daemon dies of SIGBUS). +**The VM's kernel is ahead of the panels' in one way that shows in the UI.** +It is built from `build/warden_defconfig` plus `configs/virt.fragment`, so it +has `CONFIG_BRIDGE`; the vendor 5.10 kernel most panels still run does not. +A Client-mode access point is bridged to the wired uplink and needs that, so +the Wi-Fi page offers it in the VM and says "Needs Router mode: this kernel +cannot bridge" on a 5.10 panel. Both are correct for the kernel underneath. +The difference disappears as panels move to the 6.18 build, but until then a +screenshot from here is not evidence about a 5.10 panel's Wi-Fi page. + ## Quick Start ```sh