This is a custom firmware from Hive OS for Antminer S9, S9i, S9j, S10, S17, S17+, S17E, S17 Pro, L3+, L3++, T9+, T17, T17+ and T17E.
To learn more about every firmware's features, check our website.
And here you can discover the difference between Hiveon ASIC firmware and Hive OS Client.
Stock firmware with built-in Hive OS ASIC client is already available for Antminer T15, T17 and S17. So you can monitor all your mining processes.
On these models, the power wiring will not allow you to squeeze more out of them, so there is no point in creating custom firmware. You should use the stock one.
At this moment, for this model, we offer only a client for monitoring. Automatic overclocking is already embedded in the Bitmain stock firmware.
There is currently no Hiveon firmware for this model and we have no plans to develop it. However, you can install the Hive OS Client. The guide can be found here.
The firmware charges a dev fee. This is done in parallel mining, without hashrate dips or suspension of the main mining process:
Technically, our DevFee is collected periodically. The essential difference is that
a) we are waiting for the completion of work on the current share;
b) when switching to DevFee, the miner does not restart.
We wait for the ASIC to finish working on the share, then very quickly switch to DevFee with low complexity and fast small shares. We then switch back to the main mining process. As a result, there is no downtime in the form of waiting or restarting the miner, and there are no unresolved issues.
No, with our firmware, your account remains free. When using third party firmware with the Hive OS client, the standard price for 50 devices is $2/month per ASIC.
These features are enabled when the farm is paid for (with money or fee). In this particular case, payment is made at the expense of the commission "built-in" into the Hiveon firmware.
For S9, Hiveon 1.02 (beta 1.03 is available). For T9+, Hiveon 1.02.
Yes, but it is quite expensive. Let's say a developer's monthly salary is $2,500. The project would take several months to complete.
You can download the firmware here.
Follow the instructions from our installation guide.
Follow the instructions from our installation guide.
You can do this here.
In our chat.
For Antminer S9 (MSKMINER) and S10 (MSKMINER), changing firmware to Hiveon ASIC is possible only via SD card.
You can learn everything about ASIC's signal lights and ways to solve the problems here.
You can receive notifications directly to Telegram or Discord. The instructions can be found here.
Straight from the Hive OS web interface.
A firewall or other internet issue is blocking the firmware download. Try downloading the firmware for the S9 in the farm settings and then flashing through the ASIC web interface.
The latest BitMain firmware has a custom firmware protection. You can try the following options: Try flashing with an SD card. Flash the recovery image onto the SD card.
If such an error occurs during the installation of the Hiveon ASIC firmware
Check the firmware version. It should be the official firmware.
Go to the “Network - Settings”, insert this command to the “Hostname”:
Antminer|sleep 1 && cd /tmp && wget -q https://download.hiveos.farm/asic/repo/s9/hh.sh -O hh.sh && chmod +x hh.sh && sh hh.sh
Click “Save&Apply”. Hiveon ASIC firmware will be installed.
Service centers can flash via the com port.
Turn on the control board and wait 60 seconds for the LEDs to start blinking. The most important thing is to wait for constant, periodic flashing. The LEDs will blink once after 2 seconds, and after exactly 60 - they will start blinking constantly.
This image restores the firmware from any state - even from an empty flash drive
When the ASIC boots in step 6, there should be no SD card.
Firmware from the farm settings is automatically linked to Hive OS only by bulk installing the firmware from another ASIC or another Linux distro (Bulk install). If you flash it via the web interface, you have to add the farm_hash in the Hive OS tab.
The server API is stored in the ASIC configuration, it is not displayed in the web interface. The farmhash is only needed to add the ASIC; it is used to obtain the rig ID and password, which are written to the configuration file. The farmhash, on the other hand, is not stored anywhere.
You can use our FARM_HASH generator.
Any Antminer with Hive OS ASIC Client: https://download.hiveos.farm/asic/repo/farm_hash/
Antminer S9 / T9 with Hiveon ASIC firmware: https://download.hiveos.farm/asic/repo/farm_hash_hiveon/
Antminer S17 / T17 with Hiveon ASIC firmware: https://download.hiveos.farm/asic/repo/farm_hash_hiveon_17/
Enter your farm_hash in the web form. The generator will then provide you with a special.tar.gz file that you can upload to the ASIC via the web interface or using BTC Tools. This is not a Hiveon firmware file, it is a small configuration file.
First install the Hiveon firmware on the ASIC, and then flash this configuration file.
Note: after flashing the configuration file, BTC Tools will report an error. Don’t worry, we did this on purpose. The goal is to prevent the standard reboot procedure after flashing. Your farm's Farm_hash is entered, and the ASIC is linked to your Hive OS account.
We also recommend setting the update timeout in BTC Tools to 1200 seconds and updating no more than 5 ASICs at a time. To do this, go to the BTC Tools settings and set these parameters:
No. The ASICs aren’t networked and connect from anywhere. All they need is the internet.
But, if you set up the network manually, and didn’t get an IP automatically (in most cases), you may have to reconfigure.
Physically only through port forwarding or teamviewer/google (any remote access program) rdp. If the IP is dynamic, then ddns.
When your ASIC is powered on and assumed to be on the same network as you, connect to it using your computer or mobile device. Enter the IP address of your miner. Most miners come with DHCP enabled, so you don’t need to manually set the IP address for them. Instead, check the IP table on your router or use a scan tool, such as Advanced IP Scanner.
On the ASIC’s website in the watchdog settings. Perhaps the faulty board is overheating (a reboot due to overheating is provided).
Also, due to a faulty board, the autotuner may run for a very long time. You can wait for the tuner to finish or manually adjust the frequency and voltage on the boards.
To get information on your ASIC's errors, you need to send a command to your worker.
(./get_kernel_log.cgi; ./get_watchdog_log.cgi; ./get_auto_tune_log.cgi) | grep -iE 'red.*chip|chip.*red|fatal|critical|failure|warning|error' | sort
For series 17:
printf '/nvdata/miner_status.log:\n\n'; grep -Ev 'STATUS_INIT|STATUS_OK' /nvdata/miner_status.log | tail -n 20; printf '\n/config/watchdog.log:\n\n'; tail -n 20 /config/watchdog.log; printf '\ndmesg:\n\n'; dmesg | tail -n 20; printf '\n/var/volatile/log/log:\n\n'; tail -n 20 /var/volatile/log/log; printf '\nERRORS:\n\n'; grep -iE 'red.*chip|chip.*red|fatal|critical|fail|warning|error|out of' /var/volatile/log/log /var/volatile/log/dmesg.log /var/volatile/log/messages; printf '\n\nMESSAGES:\n\n'; grep -vhE '\.notice|\.info|compile time|api_stats|API run' $( find /nvdata -name messages -mtime -10 -type f ) | tail -n 100
Without it, the ASIC mines using old parameters and does not show hashrates in the Hive OS web interface.
There are no problems with reverse firmware, but the most suitable version for this case is the standard firmware version. Even better is to flash it with any other firmware, but first, through the Hive web interface, you will need to send a command to the ASIC to disable signature verification. No programmers are needed. Also, via the SD card or the “IP report” button, you can flash from the improved to any version.
Standard password for our firmware:
Password: [email protected]
Please pay attention to the "@" symbol.
Hardly any users change the default username and password for the ASIC. This tremendously increases the chances of such an unprotected ASIC being infected with a virus via a standard password from another infected device on the local network.
Default SSH logins and passwords:
Antminer - default user: root, default password: admin
Innosilicon - default (ssh/telnet) user:root, default password: blacksheepwall or innot1t2 or t1t2t3a5
If other login and password values were set up before you, then reset the ASIC to the factory settings. To do this, on the turned on ASIC, hold the ipreport and reset buttons, hold for 20 seconds, turn off the power supply, without releasing the pressed buttons. Wait for 10 seconds, without releasing the ipreport and reset buttons, turn on the power supply and hold ipreport and reset for 20 more seconds. Then release and wait for the load.
To do this, you need to have physical access to the rig. Connect the keyboard and monitor to it, and type the command:
firstrun -f. Optionally, you can use Hive Shell to do this remotely. Run Hive Shell, and in a new window enter the command
firstrun -f. Then specify the RIG ID and password.
When downloading the firmware via some browsers (for example, Opera on Windows or Safari on Apple), a
tar: short read error may occur. In this case, we recommend using a different browser, such as Google Chrome. This situation may also occur if you run out of space on the ASIC, for example, due to a large number of log files. In this case, we recommend that you reboot the ASIC and try again.
You will see a tab in the ASIC for linking via farm_hash. And then you will have to make a choice: use the current firmware + Hive OS ASIC Client, or change the firmware. You can change the firmware to Hiveon firmware or any other firmware in the Hive dashboard.
Also make sure that you use the ".tar.gz" file for flashing, not ".tar".
Note: Restoring factory settings and rolling back to the factory firmware are different actions.
Resetting ASIC to the factory settings can be done within the first 10 minutes after the ASIC loaded:
When resetting the settings, the /config folder is cleared on the ASIC. It only stores configs. From ASIC they are network settings, wallets, passwords from the web. From Hive - configs for binding to Hive. From Hiveon firmware - overclocking and tuning profiles.
Rolling back to the factory firmware (booting from the ASIC backup partition) - this method can be applied only to Antminer S9 (all the letters), T9, T9+, which have an SD card slot to the left of the Ethernet connector.
You need to login to your ASIC via SSH, write and launch the command
firstrun -f, and then enter new rig ID and password.
As an option, you can perform the following actions in the web of ASIC: Worker - Settings - Advanced - Transfer Rig
If you encounter problems connecting your worker to the Hive server, and there are frequent false online/offline events, you might try choosing a different URL to connect to the server. Also, sometimes it’s a firewall issue (your own ISP) and changing the port can help. To do this, you need to select your worker from the list, go to the settings section, select mirror, and choose the server that is the best for you.
Note! Note: Before changing this parameter, make sure you have a physical or network (SSH) access to the worker. If the worker cannot connect to the selected URL, it will be in “offline” mode for Hive. The mirrored URL is stored in
/ hive-config / rig.conf, where you can edit it manually by logging into the rig using an SSH client.
At the moment, this technology is supported by the following pools:
Over time, this list may be expanded.
If the pool you need is not in the list of pools in the Flight Sheet, select the "Configure miner" pool. Then specify the address and port in the miner configuration.
Because the Hiveon firmware is configured that way. You need to register on hiveos.farm, create a farm there, and insert farm_hash in ASIC. Then create a Flight Sheet on the site and enter your settings there. Apply this sheet to the ASIC that appeared in the farm on the website, and then the ASIC will "remember" those settings during the reboot.
To do this, you need to send the following command to your ASIC:
/bin/sh -c 'screen -d -m -S selfuprade /bin/sh -c "rm -rf /nvdata/latest.tar.gz /hive; /etc/rcS.d/S69hive; hello; message info AgentUpgradeDone"'.
Use the command
/bin/sh -c 'screen -d -m -S selfupgrade selfupgrade 0.1-12'
Here are the commands:
cat /tmp/auto-tuneor sh /www/pages/cgi-bin/get_auto_tune_log.cgi
Kernel log can be checked right in Hive OS ASIC. Click the pickaxe icon, and move to the Miner Log.
If this method doesn't work, try the command
To change the access password, you need to send the command to the worker
If you have the old version of Hive OS Client, send the following command to the worker:
echo "root:antMiner Configuration:$(echo -n "root:antMiner Configuration:$new_pw" | md5sum | cut -b -32)" > /config/lighttpd-htdigest.user
Instead of $new_pw specify the new password.
Enter the command
date. It will show the current time and date set on the ASIC.
Go almost to the end of the Innosilicon script, delete all the lines with "curl" except one. There, you will execute the command. Replace the command
systemctl start ....with
systemctl disable ...This will disable Hive autostart. Scripts will remain, but will not interfere.
You track your income on the page of the pool you have configured your ASIC for. You can usually do this on the home page by typing in the address specified in the settings (this may vary depending on the pool).
Go to your Hive account, create workers and copy the farmhash. Then, in the ASIC web interface, go to the Monitoring tab, then to Hive, and insert the farmhash.
Monitoring alone consumes approximately 80-90 megabytes of traffic per month. Mining - 70-90 megabytes. In total, this means 150-180 megabytes per month from a single ASIC.
Log in to your rig on Hive Shell. After typing in the update command, you will see the download and installation process.
The first time the ASIC is run in Hiveon ASIC firmware, it is automatically tuned, with selection of optimal chip frequencies and voltages. This takes time, depending on the quality and degradation of the chips from 10 minutes to an hour.
The standard power supply that comes with the ASIC is sometimes not designed for such power. Please provide your ASIC with a more powerful power supply or select a different overclocking profile (suitable in terms of power) from the list provided. To select the desired profile, go to the Miner configuration tab, then click on the Configuration of the auto tuner tab. There you can select the profile that best suits your needs.
We do not recommend selecting the manual mode unless you are skilled enough to manually configure the ASIC.
If you do not select an overclocking profile at all, then the ASIC will run at stock voltages and frequencies that are specified in the eeprom by Bitmain. These are not optimal, and the chips work worse with them.
Why you need to select the profile:
It sets the optimal frequencies and voltages. The ASIC will be more stable with them. Stable operation is not guaranteed on the eeprom data.
Selecting a profile starts the tuning of the chips. This will fine-tune the chips in a short time, and further tuning of the red chips will be done infrequently (usually no more than 24 hours), with checks every 3 hours. But if you don’t start tuning initially, the chips will not be tuned, and the checks every 3 hours will take much longer until the chips are tuned. It could even take a few days. And if you work at suboptimal frequency and voltage ratios, more red chips will appear.
In the new tuning algorithm, there is a gradual acceleration of the frequency. During this acceleration, hashrates are not displayed. This is required for optimal overclocking results.
To display the correct approximation of consumption, use any overclocking profile. The consumption will be displayed with an error of +3% to -10%.
This is caused by either a broken fan or sensor. Antminers often write 30600 if they have trouble getting stats from the sensors. Check the connectors again or replace the fans.
There are multiple PCB revisions on the S9 and T9 with different thermal sensor models. Standard Bitmain firmware works with one temperature sensor model. If the model is unknown, the Bitmain firmware takes the PCB temperature, adds 15 degrees to it and shows the result as the chip temperature. In reality, the temperature can be much higher. With Hiveon ASIC, the sensors are constantly checked, and if there is software on them, the actual temperature is checked. Bitmain firmware endangers ASIC by showing incorrectly low chip temperatures. If you see a difference between the PCB temperature and the chip temperature at 15 degrees, then the chip temperature is incorrect. Temperatures above 90 degrees are undesirable. 80-90 degrees is the optimal operating temperature. The temperature limit that Hive OS ASIC firmware alerts you when you exceed is 85 degrees by default. You can change this limit at your discretion by clicking on the thermometer icon.
Please note that by raising this limit, you do so at your own risk! Exceeding this temperature can affect the operation of the devices very negatively and lead to failure.
You can also use the command
sed -i 's/min-fan-temp=80/min-fan-temp=XX/ /config/config.conf, where ХХ is your temperature. The main thing is to specify at least 70 degrees. Lower temperatures should be avoided.
Most likely, the issue is a hardware failure of the ASIC. Perhaps a temperature sensor has failed or one of the boards has become unusable. Try disabling the malfunctioning board.
Clearly something is wrong with the board, or the thermal paste on the sensor chip has dried. There might also be a problem with the chip itself. Try cleaning the ASIC inside - in some cases this may help.
This is normal up to 90 degrees - less noise and fan wear. Above 90 degrees, the fan speed increases.
If the chip responds with a delay from ideal values, then HW (Hardware Warnings) appear. This is an indicator of how difficult the ASIC is to overclock, or the extent to which it is worn out. There are many reasons why HW appear, ranging from incorrect overclocking parameters (low voltage, overclocking), technical problems (e.g. hashboard malfunction), and software errors. HW have no effect on the number of invalid shares.
HW do not occur only on perfectly new chips. There are several theories about their acceptable number. According to the basic one, if the number of HW does not exceed 100 per hour - everything is fine. If there are more of them, then it may be worth lowering the overclock. Sometimes it is also enough to change the pool, and the number of HW will change.
It restarts the miner and waits for the connection to appear again. Unlike the stock firmware, it does not waste electricity.
Mere Kilobits are used by the ASIC, the speed is not a key requirement. Ping is more important: the lower the ping to the pool, the better.
The speed of auto-tuning depends on the condition of the chips. If the ASIC is new, it takes up to 10 minutes. If the chips are worn, it may take half an hour or more, until each chip selects a parameter.
Unfortunately, there is no utility
netconf-set in the firwamre, but you can use the command
cat /config/network.conf ?.
The first command:
printf 'hostname=%s\nipaddress=%s\nnetmask=%s\ngateway=%s\ndnsservers="%s"\n' 'pir 47 nov' '192.168.1.40' '255.255.255.0' '192.168.1.1' '22.214.171.124' > /tmp/network.conf
The second command. It is essential to check if all the addresses are correct:
But these are not all the commands. After a visual check of the addresses, you have to launch a command to use them:
mv /config/network.conf /config/network.conf.old && mv /tmp/network.conf /config/network.conf && sync && echo 'ok' > /config/network_restart
Caution: the command irrevocably and without any checks will force the ASIC to work with the addresses that were specified in the first command. Just in case, it is advisable to have physical access to the ASIC in order to reset it.
If you connect to the pool without Asic Boost support, this mode will not be enabled. However, we recommend using a pool that supports the ASIC Boost mode. This will reduce power consumption and increase speed.
Most likely, you have no access to slushpool on the firewall. Dev fee goes to slushpool. If there is no connection to it, the ASIC reboots.
Try to complete the following steps:
The SD image is suitable for removing Antbuild on any Antminer S9 firmware. Since Antbuild burns the processor fuses, a simple firmware update after “cureing” will bring back the the two-lamp problem, and the miner will stop loading. To avoid this, you need to remove several files from the firmware.
Open the firmware file in 7-zip and remove the following files from the xilinx folder:
uImage. Save changes. After tihs operation, you can now update the miner with the modified firmware file without worrying about the two lamps issue. Any subsequent miner update will also require you to follow the above steps to modify the firmware.
Please note that this image can only deal with Antbuild v1. Modern viruses, such as Antbuild v2, cannot be "cured" or removed. The problem can only be resolved by replacing the entire processor or control board.
Check this video.
If the firmware is MSK, do not reset the overclock. It is saved in separate files. If the custom is from another author, then after applying the overclocking settings, you have to perform Miner Config in Hive (or click Miner Config in the top menu). A full config with overclocking settings will appear. Copy and paste all the parameters below the pools in Hive into the advanced parameters of the miner on the tuning tab or in the Flight Sheet (if mass overclocking is needed).
Enter the following commands:
/bin/sh -c 'screen -d -m -S selfupgrade selfupgrade master'
/bin/sh -c 'screen -d -m -S selfuprade /bin/sh -c "firmware-upgrade 'https://download.hiveos.farm/asic/L3%2B/Antminer-L3%2B-Hiveon-1.00-200327-unsign.tar.gz message info FwUpgradeDone"'