Luxor Technology has expanded LuxOS to another slice of the mining-hardware market, adding support for Bitmain’s Antminer Z15 Pro and WhatsMiner VH variants of the M50S and M60 that use BT1968 hashboards. The September 30 firmware release also changes WhatsMiner tuning and Bitmain installation behavior and fixes four operational bugs involving pool failover, temperature readings and fan protection.
The update matters because it is not simply another model-name addition. Firmware lives between an ASIC’s electronics and the operator’s fleet controls, so a bad sensor state, a premature fan-panic reset or an unexpected backup-pool selection can become a site-level uptime problem when multiplied across rows of machines. Luxor’s official LuxOS changelog lists all four fixes alongside the new hardware support.
The new support is specific, not universal
On the MicroBT side, this release does not mean that LuxOS only now learned how to run on the M50 family. Luxor added support in May for several M50, M50S, M50S+ and M50S++ variants. The new September release extends that work specifically to VH M50S and M60 machines fitted with BT1968 hashboards. That board-level distinction is important in an industry where two miners sold under similar model names can carry different control boards, hashboards or firmware constraints. BitcoinVersus previously explained why hashboards cannot always be swapped between ASIC models and examined how MicroBT’s WhatsMiner architecture can change materially between generations.
Luxor’s current compatibility table lists the Z15 Pro with a Xilinx control board and BEZ36501 hashboards, while its WhatsMiner list spans M50, M50S, M50S+, M50S++, M60 and M60S variants. The practical lesson for operators is familiar: verify the exact board revision before rolling firmware across a fleet.
The fan-control fixes may matter more than the headline
The release fixes a case on S19a and S19a Pro machines where a powered-off hashboard could retain frozen temperature-sensor values and keep influencing fan speed. LuxOS now allows only boards that are still running to set the fan speed. A separate fix removes boards without a usable temperature reading from the fan calculation, while another prevents a latched fan-panic state from clearing before the fans are actually observed rotating again.
Those are small software changes with physical consequences. Fans are part of the machine’s thermal-protection loop, and temperature telemetry is only useful if the firmware knows whether a reading is current, stale or invalid. BitcoinVersus has covered the same hardware-software boundary from the repair side in GoMining’s chip-level ASIC repair workflow and from the firmware side in Braiins OS 26.09 power and startup diagnostics.
Z15 Pro brings LuxOS beyond SHA-256 fleets
The Antminer Z15 Pro is an Equihash machine used for Zcash mining, not a Bitcoin SHA-256 ASIC. Luxor’s platform changelog says Commander now supports Z15 Pro installs and includes an algorithm selector for SHA-256 or Equihash views. That gives Luxor a path to reuse fleet-management ideas developed for Bitcoin miners on a different mining algorithm.
Luxor has promoted overclocking results on early Z15 Pro deployments, but the company’s documentation includes an important limitation: AutoTuner support for Antminer Equihash miners is still listed as coming soon. Z15 Pro operators can use preset profiles and monitoring now, but the automatic tuning behavior available on supported Bitcoin ASICs should not be assumed to work identically on the Z15 Pro.
LuxOS has been widening its hardware footprint
LuxOS began as third-party firmware for Bitmain Antminers. BitcoinVersus covered an earlier LuxOS release in 2024, and the competitive backdrop has changed quickly since then. In 2025, BitcoinVersus examined Bitmain’s ASIC dominance and rising competition. This year Luxor expanded LuxOS to MicroBT hardware, then continued adding specific board revisions rather than treating a miner family as one homogeneous target.
That MicroBT expansion also carries a business relationship. In April, Luxor announced that MicroBT’s investment manager had signed a term sheet for a strategic investment and that Luxor committed to a $100 million purchase of WhatsMiner hardware. Luxor said at the time that more than 300,000 Bitcoin mining machines were already running LuxOS globally. Those figures come from Luxor’s corporate announcement, not an independent fleet audit.
Why firmware consistency matters at mining scale
At one machine, firmware can look like a tuning utility. At fleet scale, it becomes part of operations. Pool priority, temperature control, fan recovery, startup behavior, logging, network access and update handling all affect whether a technician can diagnose a fault quickly or whether a problem propagates across a row. That is why the backup-pool fix in this release matters alongside the new hardware support. BitcoinVersus recently explained how Stratum connects ASIC miners to pools and how monitoring protocols fit into mine operations.
The safest deployment pattern remains staged rather than fleet-wide on day one: confirm the exact control-board and hashboard combination, test a small group of machines, compare temperatures, power, hashrate, rejected shares and recovery behavior, then expand only after the new firmware behaves correctly under the site’s real ambient and power conditions. Recent LuxOS S21++ support and signed-update work and Commander’s added hashboard support show the same pattern: board-level compatibility is becoming as important as the model name printed on the chassis.
What comes next
The next technical milestone to watch is Equihash AutoTuner support for the Z15 Pro and whatever additional MicroBT board variants Luxor validates. The September 30 release makes the firmware footprint broader, but its more consequential work may be less visible: correcting the thermal, fan and pool-state edge cases that determine whether custom firmware is dependable enough for continuous industrial use.
Leave a Reply