Luxor has expanded LuxOS again, adding support for WhatsMiner M50S and M60 “VH” variants built around BT1968 hashboards while also tightening several pieces of day-to-day miner control logic. The September 30, 2026 firmware release, which Luxor highlighted again on October 9, improves the WhatsMiner tuner, speeds up Bitmain no-SSH installation, initializes control-board LEDs even when no hashboards are detected, and fixes four operational edge cases involving pool selection, temperature data and fan safety.
The update is more consequential than a simple compatibility-list change. For large ASIC fleets, firmware is the layer that decides how the machine reacts to heat, bad sensor data, power targets, curtailment and failed components. Small control mistakes can therefore become site-wide operating problems when they are repeated across hundreds or thousands of miners.
LuxOS Adds BT1968 WhatsMiner Support
The headline Bitcoin-mining change is support for WhatsMiner M50S and M60 VH models using BT1968 hashboards. That hardware-revision qualifier matters. An M50S or M60 product name alone does not guarantee that every internal board revision is identical, so operators should verify the actual hashboard and control-board combination before deploying third-party firmware across a fleet.
Luxor’s compatibility documentation now spans selected MicroBT M50-, M50S-, M50S+-, M50S++-, M60- and M60S-family hardware. That builds on the company’s phased WhatsMiner rollout that started with M50-series support earlier in 2026. BitcoinVersus.Tech recently compared MicroBT and Canaan fleet options; firmware support is becoming another variable operators have to weigh alongside efficiency, cooling, price and repairability.
The Fan-Control Fixes Matter More Than They Look
Three of the four fixes are directly connected to temperature and fan behavior. On S19a and S19a Pro miners, LuxOS fixed a case where a powered-off board could leave behind frozen sensor readings that still influenced fan speed. The new behavior uses only boards that remain running to set fan speed. Luxor also removed boards without a usable temperature reading from the fan calculation and fixed a latched fan panic that could clear before the firmware had actually seen the fans rotating again.
That is important because the cooling loop is only as good as the data feeding it. LuxOS normally reads temperature sensors and continuously adjusts fan speed toward an operator-defined target; its temperature-and-fan documentation also describes fail-safe behavior when valid temperature data disappears. Treating stale or invalid sensor values as real can push the control loop in the wrong direction. The same principle appears in hardware troubleshooting: BitcoinVersus.Tech’s control-board overview explains why the controller is central to coordinating the rest of the miner.
The fourth fix addresses pool behavior. LuxOS says user pool groups could sometimes start on the configured backup pool instead of the primary pool. That may sound minor, but at fleet scale an unexpected pool choice can complicate hashrate accounting, monitoring and failover assumptions.
The WhatsMiner Rollout Is Moving Beyond Its M50 Starting Point
Luxor and MicroBT announced the WhatsMiner expansion in April. Luxor said at the time that more than 300,000 Bitcoin mining machines were already running LuxOS globally, while the MicroBT rollout would bring features such as Power Targeting, Advanced Thermal Management, faster hashrate ramp-up and rapid curtailment to supported WhatsMiner fleets. The announcement also included a planned strategic investment from MicroBT’s investment manager and a $100 million WhatsMiner hardware purchase commitment by Luxor.
September’s platform changelog had already added Commander-based LuxOS installation for WhatsMiner M50/M60 models. The new firmware release makes the hardware support more explicit at the hashboard level. That progression—from partnership, to installer workflow, to additional board support—is a more useful signal for operators than a broad statement that a model family is “supported.”
WhatsMiner Tuning Is Becoming Part of the Same Fleet-Control Stack
The release also says the WhatsMiner tuner has been improved. LuxOS’s AutoTuner adjusts operating parameters to find stable efficiency and performance settings, while supported power-targeting machines can move to a new wattage without a restart. That pushes firmware beyond a static configuration image and toward an active control system for the electrical and thermal behavior of the miner.
This is the same competitive direction visible in other mining firmware. Braiins OS 26.09 recently improved power and startup diagnostics, while K1Pool Firmware 1.30 added per-chip thermal downclocking. The firmware race is increasingly about how precisely software can control imperfect physical hardware under changing site conditions.
Watch LuxOS on WhatsMiner M50 and M60 Hardware
Luxor published a dedicated demonstration of LuxOS support for the WhatsMiner M50 and M60 series in September. The video below is embedded as the native responsive YouTube player rather than a thumbnail or text link.
Operators Should Verify Revisions Before a Fleet-Wide Rollout
The practical takeaway is not “flash every M60 immediately.” It is to treat firmware deployment like any other production change. Luxor’s own getting-started guidance recommends upgrading in batches so only a limited number of miners reboot at once. Operators should record the exact hashboard revision, preserve the existing configuration, confirm pool order, test fan and temperature behavior under load, and verify that monitoring systems still see the machine correctly after the upgrade.
- Confirm the miner model, control board and hashboard revision before installation.
- Stage the update on a small sample instead of the entire fleet.
- Verify primary and backup pool order after reboot.
- Check fan RPM, temperature sensors and thermal alarms under real load.
- Compare hashrate, wall power and stability before changing tuning targets.
- Review manufacturer warranty terms before using third-party firmware or overclocked parameters.
That last point matters for MicroBT hardware. The company’s current M60 warranty language excludes certain damage associated with unofficial supporting software or independently modified operating parameters such as overclocking. That does not mean every third-party firmware installation automatically produces the same warranty outcome, but operators should understand the applicable terms before changing production machines.
Why This Release Matters
Bitcoin mining hardware is becoming less useful to think about as a sealed appliance. The ASIC chips do the hashing, but the firmware increasingly determines how efficiently and safely a fleet can respond to temperature, power constraints, curtailment signals, failing boards and changing pool conditions. LuxOS adding another specific WhatsMiner board family while fixing fan-control edge cases is therefore both a compatibility story and an operations story.
The next thing to watch is how quickly Luxor expands support across additional MicroBT revisions and whether WhatsMiner tuning reaches the same maturity operators already expect from the established Antminer firmware ecosystem. The hardware competition between Bitmain, MicroBT, Canaan and newer ASIC vendors is increasingly accompanied by a second competition: who gives miners the best software control over every joule, chip and fan in the fleet.
Leave a Reply