On the shipped GUI (v0.115.0), right-clicking a stock Amlogic A113D (Antminer BHB42XXX) shows no "Install alkane OS..." option.
Root cause
board_family() (which gates the install menu via install_supported()) recognized only the Xilinx/Zynq S17 control board. A live scan of the bench A113D shows why it fell through:
asic-rs has no make for the BHB42XXX, so brand=Unknown -- board_family() bailed at the !brand.contains("antminer") guard before any control-board check.
There was no AML -> a113d mapping at all.
Meanwhile SUPPORTED_BOARDS, the from-stock install engine (stock::install_from_stock dispatches a113d -> aml_ubi) and the CLI's SUPPORTED list all already support a113d -- only this one detection gate was stale.
Fix
Map the AML (C76) control board (the a113d identity; board_labels already maps a113d -> ("AML","C76")) directly to a113d, ahead of the brand guard, since this board legitimately reports no brand. The AML code is only ever derived for an Amlogic Antminer control board, so it is specific on its own. CBE (140mm S19k/S21-class) is deliberately not mapped.
Verification (against the real bench A113D, 10.255.1.18)
Live scan now reports install=true (was false).
Unit tests pass, including a new regression test for the exact brand=Unknown BHB42XXX row.
fmt / native clippy / Windows clippy all clean locally.
Headless stock -> alkane -> stock cycle through the GUI operation layer (ALKANE_BENCH_SEQUENCE) on the releasedv0.1.0-a113d-bench1 image: PASS (install -> dropbear_2026.93 -> flag-restore -> dropbear_2018.76). Board left on pristine stock.
## Problem
On the shipped GUI (v0.115.0), right-clicking a stock Amlogic A113D (Antminer BHB42XXX) shows **no "Install alkane OS..." option**.
## Root cause
`board_family()` (which gates the install menu via `install_supported()`) recognized only the Xilinx/Zynq S17 control board. A live scan of the bench A113D shows why it fell through:
```
10.255.1.18 brand=Unknown model="Unknown: ANTMINER BHB42XXX" fw=Stock board=AML (C76) install=false
```
Two things combined, both real:
1. asic-rs has no make for the BHB42XXX, so `brand=Unknown` -- `board_family()` bailed at the `!brand.contains("antminer")` guard before any control-board check.
2. There was no `AML -> a113d` mapping at all.
Meanwhile `SUPPORTED_BOARDS`, the from-stock install engine (`stock::install_from_stock` dispatches `a113d -> aml_ubi`) and the CLI's `SUPPORTED` list **all already support a113d** -- only this one detection gate was stale.
## Fix
Map the `AML (C76)` control board (the a113d identity; `board_labels` already maps `a113d -> ("AML","C76")`) directly to `a113d`, **ahead of the brand guard**, since this board legitimately reports no brand. The `AML` code is only ever derived for an Amlogic Antminer control board, so it is specific on its own. `CBE` (140mm S19k/S21-class) is deliberately not mapped.
## Verification (against the real bench A113D, 10.255.1.18)
- Live scan now reports `install=true` (was `false`).
- Unit tests pass, including a new regression test for the exact brand=Unknown BHB42XXX row.
- fmt / native clippy / Windows clippy all clean locally.
- Headless `stock -> alkane -> stock` cycle through the GUI operation layer (`ALKANE_BENCH_SEQUENCE`) on the **released** `v0.1.0-a113d-bench1` image: **PASS** (install -> `dropbear_2026.93` -> flag-restore -> `dropbear_2018.76`). Board left on pristine stock.
Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
The right-click "Install alkane OS..." item never appeared for a stock
Amlogic A113D (Antminer BHB42XXX). board_family(), which gates the menu
via install_supported(), recognized only the Xilinx/Zynq S17 control
board, so it returned None for the A113D and the menu offered nothing.
Two things combined to hide it, both visible in a live scan of the bench
board at 10.255.1.18:
brand=Unknown model="Unknown: ANTMINER BHB42XXX" board=AML (C76)
asic-rs has no make for the BHB42XXX, so the brand is "Unknown" and
board_family() bailed at the `!brand.contains("antminer")` guard before
any board-code check; and there was no AML -> a113d mapping anyway. Yet
SUPPORTED_BOARDS, the from-stock install engine (stock::install_from_stock
dispatches a113d -> aml_ubi) and the CLI's SUPPORTED list all already
support a113d -- only this detection gate was stale.
Map the "AML (C76)" control board (the a113d identity; board_labels
already maps a113d -> ("AML","C76")) directly to "a113d", ahead of the
brand guard, since this board legitimately reports no brand. The "AML"
code is only ever derived for an Amlogic Antminer control board, so it is
specific on its own. CBE (140mm S19k/S21-class) is deliberately not
mapped.
Verified against the bench A113D: live scan now reports install=true, and
a headless stock->alkane->stock cycle through the GUI operation layer
(ALKANE_BENCH_SEQUENCE) on the released v0.1.0-a113d-bench1 image passes
(install -> dropbear_2026.93 -> flag-restore -> dropbear_2018.76).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
All checks were successful
source / check (pull_request) Skipped
verify / verify (pull_request) Successful in 30m58s
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
On the shipped GUI (v0.115.0), right-clicking a stock Amlogic A113D (Antminer BHB42XXX) shows no "Install alkane OS..." option.
Root cause
board_family()(which gates the install menu viainstall_supported()) recognized only the Xilinx/Zynq S17 control board. A live scan of the bench A113D shows why it fell through:Two things combined, both real:
brand=Unknown--board_family()bailed at the!brand.contains("antminer")guard before any control-board check.AML -> a113dmapping at all.Meanwhile
SUPPORTED_BOARDS, the from-stock install engine (stock::install_from_stockdispatchesa113d -> aml_ubi) and the CLI'sSUPPORTEDlist all already support a113d -- only this one detection gate was stale.Fix
Map the
AML (C76)control board (the a113d identity;board_labelsalready mapsa113d -> ("AML","C76")) directly toa113d, ahead of the brand guard, since this board legitimately reports no brand. TheAMLcode is only ever derived for an Amlogic Antminer control board, so it is specific on its own.CBE(140mm S19k/S21-class) is deliberately not mapped.Verification (against the real bench A113D, 10.255.1.18)
install=true(wasfalse).stock -> alkane -> stockcycle through the GUI operation layer (ALKANE_BENCH_SEQUENCE) on the releasedv0.1.0-a113d-bench1image: PASS (install ->dropbear_2026.93-> flag-restore ->dropbear_2018.76). Board left on pristine stock.Generated with Claude Code
https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
The right-click "Install alkane OS..." item never appeared for a stock Amlogic A113D (Antminer BHB42XXX). board_family(), which gates the menu via install_supported(), recognized only the Xilinx/Zynq S17 control board, so it returned None for the A113D and the menu offered nothing. Two things combined to hide it, both visible in a live scan of the bench board at 10.255.1.18: brand=Unknown model="Unknown: ANTMINER BHB42XXX" board=AML (C76) asic-rs has no make for the BHB42XXX, so the brand is "Unknown" and board_family() bailed at the `!brand.contains("antminer")` guard before any board-code check; and there was no AML -> a113d mapping anyway. Yet SUPPORTED_BOARDS, the from-stock install engine (stock::install_from_stock dispatches a113d -> aml_ubi) and the CLI's SUPPORTED list all already support a113d -- only this detection gate was stale. Map the "AML (C76)" control board (the a113d identity; board_labels already maps a113d -> ("AML","C76")) directly to "a113d", ahead of the brand guard, since this board legitimately reports no brand. The "AML" code is only ever derived for an Amlogic Antminer control board, so it is specific on its own. CBE (140mm S19k/S21-class) is deliberately not mapped. Verified against the bench A113D: live scan now reports install=true, and a headless stock->alkane->stock cycle through the GUI operation layer (ALKANE_BENCH_SEQUENCE) on the released v0.1.0-a113d-bench1 image passes (install -> dropbear_2026.93 -> flag-restore -> dropbear_2018.76). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6iView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.