How to set up a flight sheet in HiveOS for dual mining?

Dual Mining Configuration Overview

1. HiveOS supports simultaneous mining of two algorithms on compatible GPU hardware through its built-in flight sheet mechanism. This functionality relies on proper kernel-level resource partitioning and driver-aware process isolation.

2. The flight sheet acts as a runtime configuration container that defines which miner binaries execute, their launch parameters, and how system resources like VRAM, memory clocks, and power limits are allocated between the primary and secondary mining processes.

3. Dual mining is only viable on AMD GPUs with RDNA2 architecture or NVIDIA cards equipped with compute capability 6.1 and above, provided drivers meet HiveOS minimum version requirements (v0.6-224+).

4. Flight sheets must be assigned to specific rig profiles rather than applied globally, ensuring configuration integrity across heterogeneous mining farms.

Flight Sheet Creation Workflow

1. Access the HiveOS web interface and navigate to the Rig → Flight Sheet section for the target machine.

2. Click “Add new flight sheet” and select the dual mining template from the dropdown menu—options include ETH+ALPH, ETH+CFX, and BTC+ERGO depending on active pool support.

3. Define the primary miner binary path, such as /hive/miners/lolminer/1.58/lolMiner, followed by its corresponding arguments including --algo ETHASH and --pool endpoint.

4. Specify the secondary miner path and arguments in the dedicated field, ensuring non-conflicting CUDA or OpenCL device indices are declared using --devices or --gpu argument flags.

5. Save the flight sheet and assign it to the rig’s active profile before rebooting the node to initiate validation checks.

Resource Allocation Constraints

1. VRAM allocation must be manually split using --lhr_tune or --dualmode flags; automatic balancing is disabled to prevent hash rate degradation during epoch transitions.

2. Memory bandwidth throttling applies when both miners access the same GPU memory controller simultaneously—this triggers internal HiveOS warnings logged under /var/log/hive/flight-sheet.log.

3. Power limit adjustments require coordination between both miners’ TDP settings; exceeding the card’s thermal design power causes immediate watchdog-triggered restarts.

4. Clock offset values for core and memory must remain identical across both mining instances to avoid timing inconsistencies reported in the DAG verification layer.

Monitoring and Validation Signals

1. Real-time dual mining status appears in the Rig Dashboard → Miner Stats panel with separate rows for each algorithm’s accepted shares and hashrate.

2. Abnormal behavior manifests as mismatched uptime counters between miners, visible in the Processes → Running tab where one binary may show intermittent respawn cycles.

3. HiveWatch alerts trigger when combined GPU utilization exceeds 97% for more than 90 seconds, indicating insufficient scheduling headroom for background telemetry tasks.

4. Temperature spikes above 82°C on any core sensor result in automatic flight sheet suspension until manual intervention resets thermal thresholds via CLI command hive-set temp_limit 80.

Frequently Asked Questions

Q: Can I run two different miner binaries from separate vendors in one flight sheet?A: Yes, provided both binaries support the same GPU driver ABI and do not attempt exclusive device locking. Conflicts arise if either miner enforces --no-nvml or --disable-watchdog flags.

Q: Why does my secondary miner report “GPU not found” despite correct device indexing?A: This occurs when the primary miner occupies all available compute contexts. Assign explicit --device 0,1 syntax to both miners and disable auto-detection with --no-autofind.

Q: Is overclocking allowed during dual mining operations?A: Static overclocks applied via hive-config are honored, but dynamic OC profiles activated mid-mining cause instability. HiveOS disables OC application while dual mining is active unless forced with --unsafe-oc flag.

Q: Do flight sheets persist after OS updates?A: Flight sheet definitions survive minor HiveOS updates but are purged during major version jumps (e.g., v0.6 → v0.7). Always export configurations using hive-backup before initiating upgrades.