-
WarpAxe v0.1.43
Stablereleased this
2026-11-12 06:31:04 +00:00 | 123 commits to main since this releaseThe Gamma Turbo starts without a false overheat stop, and the fallback pool behaves. A fix release for what a user's Gamma Turbo showed after v0.1.42, plus two fallback-pool fixes that apply to every board. A miner on a single-chip board that has no trouble with its pools mines as before.
What is fixed.
- Two-chip boards: no overheat stop right after the chips start. Since v0.1.42 WarpAxe reads both chips' temperatures on the Gamma Turbo and the Naja Duo. On a user's Gamma Turbo this stopped the chips on every boot. While the chips are off or in reset, the second chip's diode reads the sensor's ceiling (127.875 °C), and the EMC2103 averages each diode over four conversions. So for about a second after the start, its reading still includes those ceiling values: 108 °C, then 80 °C, while the chip was really at about 50 °C. WarpAxe stopped on the first of these readings. AxeOS never switches the rail off at boot, so it never sees them. Now a second diode over the stop line in the first three readings after a chip start (rail on, reset, chain init) is held: the fans run at full and the chips keep running. If it is still over the line after that, the chips stop as before. The first chip's diode keeps its stop on the first reading. Tested on that user's Gamma Turbo: the second chip read 98.75 °C right after the start and about two seconds later both chips read 40.5 and 41.25 °C, with no stop.
- A diode stuck at the ceiling. A diode that reads 127.875 °C, the sensor's highest raw value, now counts as no reading, never as a temperature. As in v0.1.42 for a diode that gives no reading, the fans go to full and the chip with the working diode keeps the stop line.
- Shares on the fallback pool name the fallback's worker. The Stratum V1
mining.submitalways sent the main pool's worker name, also while the miner was on the fallback. A pool that checks the name (ckpool answers "Worker mismatch") rejected every share whenever the two worker names differed. Seen on a user's miner: 12 of 12 shares rejected on the fallback. This bug is older than v0.1.42. - No switch to the fallback before Wi-Fi is up. After a cold boot with a slow access point, the miner's first pool attempts failed for lack of Wi-Fi, counted as three failures, and the miner went to the fallback pool. Attempts made while Wi-Fi is not connected no longer count toward that switch. The check that switches the ASICs off when no pool answers is unchanged.
- Diagnostics file. MAC addresses (the device's own and the access point's BSSID) are now masked down to the maker's prefix. Before, they were in the file unmasked.
- Web interface. While the chain has not counted its chips yet (for example after an overheat stop before the chain start), the name plate and the chip tile show the board's chip count instead of "× 1". API:
boardAsicCountin/api/system/info.
One image for every supported board:
warpaxe.bin,warpaxe.bin.sha256,warpaxe.bin.sig; for the first installwarpaxe-factory.binandweb-flasher.tar.gz(checksums ininstall.sha256).Downloads