cwb: answer the install boot's card page, or nothing installs - #122
Merged
Merged
Conversation
The install boot runs with no network board on purpose and a ClassicWB snapshot carries no DEVS:Networks, so hardware detection and the installed-driver fallback both come back empty. The card page then opens with its ten checkboxes and none of them ticked, the run clicks Proceed at every page, and the Installer refuses the lot: measured 2026-09-30, 145 clicks, the 150-poll cap, nothing installed. An empty drive passes every "this file is absent" assertion this harness makes, so that reads as a harness that never got started rather than as the page it could not answer. installdrive has carried DRIVE_PICK_OPTIONS and DRIVE_PICK_ID since it was written, and nothing ever passed them: the compile line below handed it DRIVE_LEVEL, DRIVE_RUNS and DRIVE_YES_LABEL only, which answers a yes/no page and cannot touch a page of ten options. Pass ten options and gadget 4, "A2065" -- the board BOARD stages for the standing boot, which is what keeps the tick in agreement with the driver_match gate that runs after the install. Both are knobs, because the option count and the gadget order belong to Install-AmiNetXDuo's script rather than to this harness. The path was unexercised for so long because nothing runs it: ci.yml lists tools/classicwb.sh in a lint file list, not in a job, so no CI run has reached this line since the harness was last touched. Verified on playhouse3 with the two knobs set: the install completes, all five gates report ok and the instance comes up on the network. Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tools/classicwb.shcannot install anything today, and this is the two-word fix.What happens
The install boot runs with no network board on purpose and a ClassicWB snapshot carries no
DEVS:Networks, so hardware detection and the installed-driver fallback both come back empty. The card page opens with its ten checkboxes and none of them ticked, the harness's click loop presses Proceed at every page, and the Installer refuses the lot.Measured 2026-09-30 on playhouse3: 145 clicks, the 150-poll cap,
install_status=20, nothing installed. The failure then hides itself, because an empty drive passes every "this file is absent" assertion the harness makes.Why
install/test/installdrive.chas carriedDRIVE_PICK_OPTIONSandDRIVE_PICK_IDsince it was written. Nothing ever passed them — the compile line handed itDRIVE_LEVEL,DRIVE_RUNSandDRIVE_YES_LABEL, which answers a yes/no page and cannot address a page of ten options.PICK_OPTIONSPICK_IDBOARDstages for the standing bootThe second row is the one that matters: because the tick is the same board
tools/sana2-stage.shstages, it cannot disagree with thedriver_matchgate that runs after the install. Both are env-overridable, since the option count and gadget order belong to Install-AmiNetXDuo's script rather than to this harness.Why it went unnoticed
Nothing runs this path.
ci.ymlliststools/classicwb.shin a lint file list, not in a job, so no CI run has reached this line since the harness was last touched.Evidence
With the two knobs set on playhouse3: the install completes, all five gates report ok, and the instance comes up on the network with its web shell. Without them: the run above.
One file,
tools/classicwb.sh. No shipping surface —tools/is not on it, so the changelog gate wants this in the git log.🤖 Generated with Claude Code