Market Cap: $2.219T -3.80%
Volume(24h): $129.2422B -1.59%
Fear & Greed Index:

23 - Extreme Fear

  • Market Cap: $2.219T -3.80%
  • Volume(24h): $129.2422B -1.59%
  • Fear & Greed Index:
  • Market Cap: $2.219T -3.80%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top Cryptospedia

Select Language

Select Language

Select Currency

Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos

How to use HiveOS for remote mining management? (Installation)

Ensure GPU compatibility (AMD RDNA2/3 or NVIDIA Ampere+), update BIOS, disable Fast/Secure Boot, validate & flash HiveOS image correctly, then register via web UI.

Apr 04, 2026 at 05:39 pm

System Requirements and Pre-Installation Checks

1. Verify that the target mining rig runs a compatible GPU architecture—HiveOS officially supports AMD RDNA2, RDNA3, and NVIDIA Ampere or newer GPUs for optimal hash rate stability.

2. Ensure the motherboard BIOS is updated to the latest version supportingResizable BAR and PCIe bifurcation if multi-GPU setups are intended.

3. Confirm network connectivity: static IP assignment or DHCP reservation is strongly recommended to maintain persistent SSH and web interface access.

4. Disable Fast Boot and Secure Boot in UEFI settings to prevent kernel module loading failures during HiveOS boot initialization.

5. Prepare a USB 3.0 flash drive with minimum 8GB capacity formatted as FAT32 using tools like Rufus or BalenaEtcher.

Flashing HiveOS Image to Boot Media

1. Download the latest stable HiveOS image from the official hiveos.farm domain—avoid third-party mirrors due to checksum integrity risks.

2. Use sha256sum on Linux or CertUtil on Windows to validate the downloaded .img.xz file against the published hash on the release page.

3. Decompress the archive using xz -d command before writing; attempting direct write of compressed image leads to unbootable media.

4. Write the decompressed .img file using dd on Linux (sudo dd if=hiveos.img of=/dev/sdX bs=4M status=progress) or Win32 Disk Imager on Windows.

5. Safely eject the USB device after completion—interrupted writes result in corrupted bootloader sectors and failed PXE fallback attempts.

Initial Boot and Network Registration

1. Insert the USB drive into the mining rig and power on while pressing F12 or ESC to invoke one-time boot menu—select USB-HDD entry explicitly.

2. Observe the GRUB menu timeout: press 'e' to edit kernel parameters if the rig fails DHCP—append ip=dhcp or ip=192.168.1.100::192.168.1.1:255.255.255.0:hive-rig:eth0:none manually.

3. After successful boot, the system displays a local IP address on screen—this must be entered into a browser on a management workstation.

4. Log in via the web UI using default credentials: user hive, password hive—immediate password change is enforced after first login.

5. Navigate to Settings → Farm → Register Rig and paste the unique registration key obtained from hiveos.farm dashboard under your farm profile.

GPU Detection and Driver Initialization

1. HiveOS auto-detects GPU models but may misidentify certain OEM variants—cross-check lspci -v output against supported device IDs listed in hiveos.farm/docs/hardware.

2. AMD rigs require amdgpu-pro or open-source amdgpu drivers; HiveOS selects based on detected ASIC generation—manual override is possible via CLI using hive-set gpu_driver.

3. NVIDIA rigs load nvidia-driver-535 by default; legacy cards like GTX 10-series require explicit downgrade to nvidia-driver-470 using hive-update --driver 470.

4. Run hive-check-gpu to verify VRAM temperature reporting, PCIe link width negotiation, and memory clock lock status—values outside ±5% of spec indicate hardware or BIOS issues.

5. Enable GPU persistence mode via hive-set gpu_persistence on to prevent driver reload delays during miner restarts.

Frequently Asked Questions

Q: Can HiveOS be installed on NVMe-only systems without SATA or USB boot capability?A: Yes—HiveOS supports PXE boot from network TFTP servers. Configure DHCP option 66 and 67 correctly, and ensure UEFI firmware enables IPv4 PXE stack.

Q: Why does hive-list show offline status even though the rig responds to ping?A: The HiveOS agent daemon may not be running—verify with systemctl status hive-agent; restart with systemctl restart hive-agent if inactive.

Q: Is it safe to run hive-update --force on production rigs?A: Not recommended—forced updates bypass compatibility checks and may introduce miner binary incompatibility with current overclock profiles.

Q: How do I recover access if the web UI password is lost and SSH is disabled?A: Boot into GRUB, press 'e', append init=/bin/bash to kernel line, remount root as rw with mount -o remount,rw /, then use passwd hive to reset credentials.

Disclaimer:info@kdj.com

The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!

If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.

Related knowledge

See all articles

User not found or password invalid

Your input is correct