Skip to content

CatStack 2.0.2 RC2 - Linux owner voltage controls

Pre-release
Pre-release

Choose a tag to compare

@JustAResearcher JustAResearcher released this 08 Nov 18:12

CatStack 2.0.2 RC2

RC2 fixes core voltage remaining unavailable on Linux RTX 40/50 Vast owner rigs because the manager previously required a temporary qualification file. The Tuning panel now offers Pause Vast listing & enable core voltage, which verifies ownership and zero allocations, pauses the idle offer and enables the field. CatStack renews the normal owner authorization while running. The supervisor restores zero if verification expires or rental/listing state changes. Restore core voltage & end tuning ends the session; the listing stays paused until the owner resumes it in Vast. This update does not add native Windows GPU voltage control.

Core-voltage tuning and the voltage-field keyboard-focus fix follow the existing 2.0.1 RC3 release. Application VERSION is 2.0.2 and the prerelease identity is 2.0.2-rc2.

  • Core-voltage demand offset from -300 to 0 mV in 5 mV steps, with global and per-GPU settings, saved profiles and CLI support.
  • GeForce RTX 40- and 50-series model eligibility, including Ti, SUPER, D and laptop variants. Actual availability still requires an inspected matching NVIDIA Linux driver/API library, the correct generation layout and verified control readback. The Windows manager controls supported Linux rigs; native Windows GPU core-voltage control remains unavailable.
  • Fifteen-minute probation, continued monitoring, independent systemd recovery and rental-host protections. Existing profiles do not automatically opt in. Zero restores the original demand.
  • Live fleet updates preserve focus while entering a negative voltage value. Per-GPU input boxes are wider and their table scrolls within its panel.
  • Retains 2.0.1 RC3's Push SSH Key retry and authentication messages, current-run OC error reporting, headless NVML offsets, native NVIDIA memory/hotspot temperatures, current SSH miner output, and automatic-update/discovery repair with customer-workload deferral.
  • Retains AMD support and the 45-day unused-flight-sheet retention introduced in the later beta snapshots.

Qualification is specific to the card, clock and workload. The full manual offset range has not been qualified for stability. Deep RTX 5070 Ti trials at -100/-125 mV caused firmware hangs requiring recovery; software rollback cannot guarantee restoration after a firmware hang. Measured power comparisons used NVIDIA board-power telemetry and miner hashrate, rather than wall-meter energy.

Extract the manager archive to a new folder and use the existing farm-data directory. Verify the archive against its SHA-256 sidecar. No new MeowOS disk image is included and no rig reflash is required.

RC2 validation: 619 Windows tests passed with 11 Linux-runtime checks skipped; all 630 Linux tests passed. Twelve rendered desktop/mobile checks cover owner preparation/reset and uninterrupted voltage entry. A live RTX 5080 on NVIDIA 595.91.07 completed normal owner preparation, applied and read back -5 mV, and independently restored 0 mV when manager renewal stopped. The original Vast offer and terms were restored. This verifies the normal product path, not only the model-name eligibility check.

Build source snapshot (private): 5fbd4c10784ad4fb4430ba1cf65f21a2b292d466. Both manager packages include compiled Linux worker 0.4.27; application source is not published. Packaged CLI/profile and HTTP API identity checks passed on Windows and Linux, and the Windows sensor passed its self-test.