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 client is already available for Antminer T15, T17 and S17. So you can monitor all your mining processes.
On these models the power wiring won’t allow to squeeze more out of them, so it makes no sense to make 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.
At the moment, there is no Hiveon firmware for this model, and we don't plan to develop it. However, you can install Hive OS Client. The guide is here.
The firmware takes a dev fee. This is done in parallel mining, without hashrate dips or suspension of the main mining process:
Technically, our DevFee is implemented in time. 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 ASIC to complete the work on the share, then very quickly switch to DevFee of low complexity, with fast small shares, then switch back to the main mining. As a result, there is no downtime in the form of waiting, restarting the miner, and no unresolved issues.
No, with our firmware your account remains free. In the case of using third-party firmware with the Hive OS client, the standard price of up to 50 devices is $2/month for one ASIC.
These features are enabled when the farm is paid (with money or fee). In this particular case, the 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 that's pretty expensive. Let's say, the developer's salary is $2500 per month. The project will take several months.
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.
Firewall or another internet issue blocks the firmware download. Try to download the firmware for the S9 in the farm settings and then flash through the ASIC’s web interface.
The latest BitMain firmware enables protection against custom firmware. You can try the following options: Try to flash through using an SD card. Flash the recovery image onto the SD card
In case you see such an error when installing Hiveon ASIC firmware:
Check out the version of firmware. It should be 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
Hiveon ASIC firmware will be installed.
Service centers can flash through the com port.
Turn on the control board and wait 60 seconds till the LEDs start flashing. The main thing is to wait for a constant periodic flashing. The LEDs will blink once after 2 seconds, and exactly after 60 - they will start flashing constantly.
This image restores the firmware from any state - even with an empty flash drive.
At the time of the launch of ASIC in step 6, there should be no SD-card.
The firmware from the farm settings is automatically tied to Hive OS only via bulk installation of the firmware from another ASIC or another Linux distro (Bulk install). If flashing through the web interface, you need to add the farm_hash in the Hive OS tab.
The server API is saved in the ASIC configuration, it is not displayed in the web interface. Farmhash is needed only to add the ASIC, rig ID and password are obtained with its help, which are saved to the config file. And the farmhash is not saved anywhere.
You can use our FARM_HASH generator.
Any Antminer with Hive OS Client for ASIC: 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/
You should enter your farm_hash in the web form. The generator then provides you with the special.tar.gz file, which 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 you should install Hiveon firmware on the ASIC, and then flash this configuration file.
Please 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 binded to your Hive OS account.
We also recommend you to set the update timeout in BTC Tools to 1200 seconds and update 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 tied to networks and connect from anywhere, all they need is internet.
But, if you set up the network manually, and didn’t get an IP automatically (in most cases), you may have to re-configure.
Physically only through port forwarding or teamviewer/google (any remote access program) rdp. If the IP is dynamic, then ddns.
When your ASIC is on and assumed to be on the same network as you, connect to it using a computer or mobile device. Enter the IP address of your miner. Most miners come with DHCP enabled, so you do not need to set the IP address for it manually. Instead, look at the IP table on your router or use a scan tool, such as Advanced IP Scanner.
On the ASIC’s web in the settings of the watchdog. Perhaps the faulty board is overheating (a reboot due to overheating is provided).
Also, due to a faulty board, the autotuner can work for a very long time. You can wait for the tuner to finish working or manually set the frequency and voltage settings 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 doesn’t show hashrates in Hive OS web interface.
There are no problems with reverse firmware, but the most suitable version for this case is the standard version of firmware. Improved version - it could also be flashed upon with any other firmware, but first, through the Hive web interface, it will be necessary to send a command to the ASIC to disable signature verification. No programmers are needed. Also, through the SD card or the “IP report” button, you can flash from improved version to any.
Standard password for our firmware:
Password: [email protected]
Please pay attention to the "@" symbol.
Almost all users do not change the default username and password for an ASIC. Soon, such an unprotected ASIC will be 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 enter the command:
firstrun -f. As an option, you can use Hive Shell to do this remotely. Launch Hive Shell, and in a new window enter the command
firstrun -f. After this specify RIG ID and password.
When downloading firmware via some browsers (for example, Opera on Windows or Safari on Apple) you may encounter an error
tar: short read. In this case, we recommend using a different browser, such as Google Chrome.
Also, this situation may occur if there is no space on the ASIC, for example due to the large number of log files. In this case we recommend to reboot the ASIC and try again.
There will appear a tab in ASIC for linking via farm_hash. And then you will have to make a choice: to use the current firmware + Hive OS Client, or to change the firmware. You can flash to Hiveon or any other firmware in the Hive dashboard.
Please, also make sure that for flashing you use the ".tar.gz" file, not ".tar".
Please note: resetting to the 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 ASIC has loaded:
When resetting the settings the folder /config is cleaned on the ASIC. Only configs are stored in it. From ASIC they are network settings, wallets, password from the web. From Hive - configs for binding to Hive. From Hiveon firmware - overclock and tune 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 have problems connecting your worker to the Hive server, and often there are false events online/offline, you can try choosing a different URL to connect to the server. Also, sometimes there is a problem with the firewall (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 a mirror, and select the server that is suitable for you.
Please note! Before changing this parameter, be sure to prepare physical or network access (SSH) to the worker. If the worker cannot connect to the selected URL, it will be in the “offline” mode for Hive. The mirrored URL is saved in
/ hive-config / rig.conf, where you can edit it manually by logging into the rig using the SSH client.
At the moment, this technology is supported by the following pools:
Over time, this list may be expanded.
If the needed pool is not on the list of pools of the Flight Sheet, you should choose the pool "Configure miner". Then, in the miner configuration, specify address and port.
Because the Hiveon firmware is so configured. You need to register on hiveos.farm, create a farm there, and insert farm_hash in ASIC. Next, 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 site, and after that the ASIC will "remember" these 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:
Kernel log can be checked right in Hive OS. Click the pickaxe icon, and move to the Miner Log. If this method doesn't work, try 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 can follow your income on the page of that pool to which you configured your ASIC. Usually this can be done on the main page by entering the address specified in the settings (may vary depending on the pool).
Go to your Hive account, create workers and copy the farm_hash. Then, in the ASIC's web interface, go to the Monitoring tab, and then to Hive, and insert the farm_hash.
Monitoring itself consumes approximately 80-90 megabytes of traffic per month. Mining - 70-90 megabytes. In total, this means 150-180 megabytes per month from one ASIC.
Log into your rig on Hive Shell. After entering the update command, you will see the download and installation process.
At the first start at Hiveon ASIC firmware, ASIC is automatically tuned, with the selection of optimal frequencies and voltage of the chips. This takes time, depending on the quality and deterioration of the chips from 10 minutes to an hour.
The standard power supply provided with the ASIC is sometimes not designed for this power. Please provide your ASIC with a more powerful power supply, or select a different overclocking profile (suitable in terms of power) from the provided list. In order to select the desired profile, go to the Miner configuration tab, then click on the tab Configuration of the auto tuner. There you can choose the profile that suits your needs best.
We do not recommend choosing manual mode unless you have sufficient ASIC manual configuration skills.
If you do not select an overclocking profile at all, then the ASIC will operate at stock voltages and frequencies that are specified in the eeprom by Bitmain. They are not optimal, and the chips work with them worse.
Why do you need to select the profile:
It sets the optimal frequencies and voltages. ASIC will work more stably on them. Stable performance is not guaranteed on data from eeprom.
Profile selection launches the tuning of chips. This will fine-tune the chips in a short time, and further tuning of the red chips will be done seldom (usually it doesn't take more than 24 hours), with a check every 3 hours. But if you don’t initially launch the tuning, the chips will not be tuned, and the check every 3 hours will take much more time, until the chips are tuned. It can even take days. And if you work at sub-optimal frequency and voltage ratios, more red chips will appear.
In the new tuning algorithm, there is a gradual acceleration in frequency. During this acceleration, the hashrates aren’t displayed. This is required for optimal overclocking results.
To display a correct approximation of consumption, any overclocking profile should be applied. Consumption will be displayed with an error from +3% to -10%.
This is caused either by a broken fan or sensor. Antminers often write 30600 if they have a problem with obtaining stats from sensors. Recheck the connectors or replace fans.
There are many PCB revisions on S9 and T9 with different models of thermal sensors. Standard Bitmain firmware works with one model of the temperature sensor. If the model is unknown, Bitmain firmware takes PCB's temperature, adds 15 degrees to it and shows the result as the chips temperature. In fact, the temperature can be much higher. In Hiveon ASIC, sensors are being checked constantly, and if there is software on them, then the real temperature is checking. Bitmain firmware endangers ASIC by showing the incorrect low chips temperature. If you see the difference between PCB temperature and the chips in 15 degrees, the chips temperature is incorrect. The temperature above 90 degrees is undesirable. 80-90 degrees is an optimal working temperature. The temperature limit after which the alert comes in Hive OS is set to 85 degrees by default. You can change this limit as you wish by clicking on the thermometer icon.
Please note that by raising this limit, you do everything at your own risk! Exceeding this temperature can affect the performance of the devices in a very negative way, and lead to their 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 matter is in ASIC hardware malfunction. Perhaps the temperature sensor has failed or one of the boards has become unusable. Try disabling the malfunctioning board.
Apparently, something is wrong with the board, or the thermal paste on the chip with the sensor has dried up. There may also be a problem with the chip. Try cleaning the ASIC inside - in some cases, this may help.
This is normal up to 90 degrees - less noise and fan wear. After 90 degrees the fan speed will increase.
If the chip responds with a delay relative to perfect values, then HW (Hardware Warnings) appear. This is an indicator of how hard it is for the ASIC to overclock, or to what extent it is worn out. There are many reasons for the occurrence of HW: starting from incorrect overclocking parameters (low voltage, overclock), technical problems (for example, hashboard malfunction) and ending with software errors. HW don’t affect the number of invalid shares.
HW do not occur only on perfect new chips. There are several theories regarding their allowable number. According to the basic one, if the number of HW does not exceed 100 per hour - everything is fine. If there are more, 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 reappear. In contrast to the stock firmware, it doesn’t waste electricity.
Mere Kilobits are used by the ASIC, the speed is not a main requirement. Ping is more important: the lower the ping to the pool, the better.
The speed of auto-tuning depends on the state of the chips. If the ASIC is new, it takes up to 10 minutes. If the chips are worn, it could 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' '220.127.116.11' > /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 desirable to be able to physically access the ASIC to reset it.
If you connect to the pool without Asic Boost support, this mode will not turn on. 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 regular firmware update after the “cure” will return the problem of two lamps, and the miner will stop loading. To avoid this, you need to delete several files from the firmware.
Open the firmware file in 7zip and delete the following files from the folder xilinx:
uImage. Save the changes. After that you can update the miner using the modified firmware file without fear of the two lamps issue. Any subsequent miner update will also require completing the above steps to modify the firmware
Please note that this image can deal only with Antbuild v1. Modern viruses, such as Antbuild v2, cannot be "cured" or removed. The issue can only be resolved by replacing the entire processor or control board.
Check this video.
If the firmware is MSK, then overclocking should not be reset. It is written in separate files. If the custom is from another author, then after applying the overclocking settings, you need to perform Miner Config in Hive (or click Miner Config in the top menu). The full config with overclocking settings will come back. 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"'