home · pool · blog · knowledge base · changelog · source · statistics · support · sampleconf · ConfigMaker · buy ethOS · mining calculator
Table of Contents
Getting Support
Quick Start Guide
Video Guides
Mining Zcash
Mining Monero
Adding newer claymore to ethOS
Adding newer claymore-zcash to ethOS
Adding newer optiminer-zcash to ethOS
Updating ethOS to the latest version
Mining with RX 400 Series
Writing ethOS to SSD on Windows
Writing ethOS to SSD on Linux (debian/ubuntu flavors)
Initial Setup (using a keyboard and monitor on ethOS)
Booting into ethOS
Using SSH to login to ethOS from Windows
Setting ethOS to single-rig mode
Setting and Switching your Wallet and/or Pool
Using a Pool that requires workers, usernames, and passwords (suprnova)
Setting up your own remote config
Using ConfigMaker.com for your remote config
Setting up a DigitalOcean droplet for your remote server
Setting a static internal IP for your ethOS rig
Overclocking
Managing temperature
Setting a custom Panel ID
Fixing unexpected low pool hashrate
Autotrading Altcoins for Bitcoin
Mining and Common Issues
Provisioning AMD boards
Provisioning Intel boards
Fixing 290/390/470/480 boot problems with Intel boards
Fixing ADL Error / Hardware Error

Getting Support

There is no email or skype support for ethOS.

If you need help with ethOS, talk to us in IRC (#ethosdistro on Freenode).

Generating a Diagnostics File
  1. Wait for your rig to enter its crashed, broken, or non-working state.
  2. Run gethelp in a terminal while connected to your rig, and copy/save the output link.
  3. Connect to IRC with the below instructions.
  4. Once connected, paste the gethelp link in channel, describe the issue in your own words, include recent changes and any troubleshooting steps that you have done.
  5. Wait for a reply and talk in channel.
IRC in your browser
  1. On your regular PC or computer, visit https://webchat.freenode.net/?channels=ethosdistro.
  2. Enter a nickname for yourself.
  3. Do not change the "channels" field.
  4. Do not checkmark "auth to services".
  5. Checkmark "i'm not a robot".
  6. Click connect and wait up to 15 seconds to connect to the IRC channel.
IRC on your IRC Client

Channel: #ethosdistro
Server: irc.freenode.net
Port: 6667

IRC on your local rig
  1. Run ethoschat-local in your ethOS terminal.
  2. Wait up to 15 seconds for your rig to join the IRC channel.
  3. ALT+TAB between the regular Terminal and the ethoschat Terminal.
  4. To quit ethoschat, run /exit inside of the ethoschat Terminal and ALT+TAB to the regular Terminal.
IRC on your rig via SSH
  1. Run ethoschat in your SSH session.
  2. Wait up to 15 seconds for your rig to join the IRC channel.
  3. To quit ethoschat, run /exit inside of your SSH session.

Quick Start Guide

  1. Run helpme to get a list of commands, your stats panel link, and rig status.
  2. Set ethOS to single-rig mode.
  3. In /home/ethos/local.conf , change "0x0bdC4F12fB57d3acA9C3cF72B7AA2789A20d27f2" to your wallet.
  4. IF AND ONLY IF you have RX 400 series GPUs, enable the amdgpu driver.
  5. Change user "ethos" password with passwd ethos to secure your rig.
  6. Reboot with r.

NOTE: ethOS is set to mine to the ethOS etheruem pool. Check your mining statistics at http://ethosdistro.com/pool/


Video Guides


Mining Zcash

  1. Update ethOS.
  2. Get started with the Quick Start Guide.
  3. Set globalminer claymore-zcash or miner [worker] claymore-zcash in config.
  4. Set proxywallet to your zcash wallet.
  5. Set proxypool1to your zcash pool (example pools: flypool and nanopool).
  6. Optional: Set -i flag to set intensity: flags -i 3 OR flg [worker] -i 3
  7. If you experience crashing, revert to all stock clocks, check again, then revert to stock bios (flip GPU bios switch).

Mining Monero

  1. Update ethOS.
  2. Get started with the Quick Start Guide.
  3. Set globalminer sgminer-gm-xmr or miner [worker] sgminer-gm-xmr in config.
  4. Set proxywallet to your Monero wallet. NOTE: If mining to exchange, you need proxywallet wallet.paymentid
  5. Set proxypool1 and proxypool2 to your Monero pools (both pools must be defined).
  6. If you have 2GB GPUs, set rawintensity to a lower value in /home/ethos/sgminer-gm-xmr.stub.conf
  7. If you experience crashing, revert to all stock clocks, check again, then revert to stock bios (flip GPU bios switch).
  8. If miner fails, remove both .WORKER from /home/ethos/sgminer-gm-xmr.stub.conf (some pools do not accept worker well).

Adding newer claymore to ethOS

Due to the speed of incremental improvements of claymore, you can insert the new miner into ethOS.

  1. Update ethOS.
  2. Make sure your GPUs are not in a crashed state. It is best to proceed immediately after a reboot.
  3. become root with sudo su (password: live)
  4. Set globalminer claymore or miner [worker] claymore in config.
  5. cd /opt/miners/ && disallow && minestop && rm -f /opt/miners/claymore-latest.tar.gz
  6. wget http://update.ethosdistro.com/miners/claymore/claymore-latest.tar.gz
  7. tar -xvf claymore-latest.tar.gz -C /opt/miners/claymore --strip-components=1
  8. chown -R ethos:ethos /opt/miners/claymore/* && chmod +x /opt/miners/claymore/ethdcrminer64
  9. service ethos-miner-monitor restart && allow && show miner
  10. See the Claymore Bitcointalk thread for configurations options that can be set in /home/ethos/claymore.stub.conf

NOTE: If you have many rigs, use the above as a guideline for your own distribution method.
If any problem occurs and you would like to revert, run: ethos-update reupdate


Adding newer claymore-zcash to ethOS

Due to the speed of incremental improvements of claymore-zcash, you can insert the new miner into ethOS.

  1. Update ethOS.
  2. Make sure your GPUs are not in a crashed state. It is best to proceed immediately after a reboot.
  3. become root with sudo su (password: live)
  4. Set globalminer claymore-zcash or miner [worker] claymore-zcash in config.
  5. cd /opt/miners/ && disallow && minestop && rm -f /opt/miners/claymore-zcash-latest.tar.gz
  6. wget http://update.ethosdistro.com/miners/claymore-zcash/claymore-zcash-latest.tar.gz
  7. tar -xvf claymore-zcash-latest.tar.gz -C /opt/miners/claymore-zcash --strip-components=1
  8. chown -R ethos:ethos /opt/miners/claymore-zcash/* && chmod +x /opt/miners/claymore-zcash/claymore-zcash
  9. service ethos-miner-monitor restart && allow && show miner

NOTE: If you have many rigs, use the above as a guideline for your own distribution method.
If any problem occurs and you would like to revert, run: ethos-update reupdate


Adding newer optiminer-zcash to ethOS

Due to the speed of incremental improvements of optiminer, you can insert the new miner into ethOS.

  1. Update ethOS.
  2. Make sure your GPUs are not in a crashed state. It is best to proceed immediately after a reboot.
  3. become root with sudo su (password: live)
  4. In your config, set globalminer optiminer-zcash or miner [worker] optiminer-zcash
  5. cd /opt/miners/ && disallow && minestop && rm -f optiminer-zcash-latest.tar.gz
  6. wget http://update.ethosdistro.com/miners/optiminer-zcash/optiminer-zcash-latest.tar.gz
  7. tar -xvf optiminer-zcash-latest.tar.gz && chown -R ethos:ethos /opt/miners/optiminer-zcash/*
  8. service ethos-miner-monitor restart && chmod +x /opt/miners/optiminer-zcash/* && allow && show miner

NOTE: If you have many rigs, use the above as a guideline for your own distribution method.
Reduce clocks slightly if it crashes. If any problem occurs and you would like to revert, run: ethos-update reupdate


Updating ethOS to the latest version

  1. Read the changelog for very important major changes.
  2. Become physicaly local to your rigs. Do not update remotely.
  3. Run: sudo repair-ethos-update && sudo ethos-update && sleep 5 && r    (do not interrupt the update process).
  4. Do not interrupt the update process. After the reboot, watch your rig come up.
  5. ONLY IF your rig fails immediately after updating and rebooting, reupdate your rig: sudo ethos-update reupdate && sleep 5 && r

Mining with RX 400 Series

AMD requires the use of the AMDGPU driver for the RX 400 Series. All older GPUs are best supported by the old FGLRX driver. Because of this, you cannot mix and match the RX 400 series with any other series in the same rig.

To switch to AMDGPU, follow the below instructions:

  1. Open your config for editing:
    • If in single-rig mode, add globaldriver amdgpu to your config.
    • If you are using remote.conf, set driver [worker] amdgpu to your config, and then run putconf ([worker] is your 6-digit rig name).
  2. Wait for the reboot (if a reboot does not catch within one minute, run ethos-switchdriver amdgpu)
  3. After your rig reboots, you will be able to use the RX 400 series.
  4. Optional: Follow the overclocking guide. If increasing core/mem on AMDGPU, set pwr [worker] 7 OR globalpowertune 7.

Writing ethOS to SSD on Windows

NOTE: ethOS should only be written to a 16gb+ SSD (not an HDD or USB drive).

  1. Download and unzip the downloaded file with 7-zip, it will extract into approximately a 7.5gb image.
  2. Use Raw Copy Tool (available at http://hddguru.com/software/HDD-Raw-Copy-Tool/ ).
  3. Plug in the destination SSD to the sata power cable first, then to the sata data cable. Raw Copy Tool will recognize the drive and allow you to clone the ethOS iso onto the drive, sector for sector.

Writing ethOS to SSD on Linux (debian/ubuntu flavors)

NOTE: ethOS should only be written to a 16gb+ SSD (not an HDD or USB drive).

  1. Download and uncompress the downloaded file with unxz /path/to/ethos.xz, it will extract into approximately a 7.5gb image.
  2. Confirm the location of your source ethOS sio file file:
    ls /path/to/ethos.iso
  3. Physically attach your destination SSD to the sata power cable first, then to the sata data cable.
  4. Confirm that your rig sees your destination drive. You should see the destination drive appear as /dev/sdX where X is your enumerated drive (i.e. /dev/sdb):
    dmesg | grep sd
    fdisk -l | grep sd
  5. Confirm that your destination drive is correct with smartctl:
    apt-get -fy install smartmontools
    smartctl -i /dev/sdX (replace X with your enumeration)
  6. Clone your source to your destination. VERY IMPORTANT, if you make a mistake and accidentally clone to a different drive, you will cause CATASTROPHIC DATA LOSS.
    apt-get -fy install gddrescue
    ddrescue --force -r2 /path/to/ethos.iso /dev/sdX (replace X with your enumeration)
  7. Watch the progress. ddrescue should finish with no errors after it clones 16gb worth of data. After it is done, it is safe to shutdown and power off your rig. The ethOS drive is now ready for use.

Initial Setup (using a keyboard and monitor on ethOS)

During initial setup, you can connect a keyboard and monitor to your rig to watch it boot up.

  1. Without using a riser, attach a GPU to the gpu0 PCI-E slot on your motherboard. (ignore all 1x slots, the gpu0 PCI-E slot in always the 16x PCI-E slot that is physically closest to your motherboard's CPU socket).
  2. Attach a monitor to the left-most DVI port of gpu0. If you incorrectly connect your monitor to another GPU or to onboard video, you will get a blank display.
  3. If your rig POSTs, you will see a GPU detection screen during bootup. If your rig does not POST, power off. Check to make sure the CPU cable is seated properly, and try different RAM in different slots.
  4. ethOS will boot to the desktop automatically. After your rig boots successfully, all interaction with ethOS is done via the terminal screen.

If fewer GPUs show up here than are connected to your rig, check all connections and reboot, If some GPUs are still missing, it is a hardware, riser, or motherboard bios problem, not a software problem. No linux command will fix this.


Booting into ethOS

  1. Plug the ethOS SSD into a SATA power and a SATA data cable.
  2. Boot the rig.
  3. The rig will boot to the ethOS desktop, and the fans will ramp up. The fan ramp-up is normal and is not indicative of a crash.

If your rig fails to boot due to "initramfs" error, or boots directly to BIOS, proceed with the below instructions:

  1. Power off your rig.
  2. Try a few different SATA ports on your motherboard, some may be disabled in BIOS.
  3. Try a different SATA power connection, it may not be seated properly.
  4. Try a different SATA data cable, it may be faulty.

If your rig continues to fail to boot, try the below options:


Using SSH to login to ethOS from Windows

  1. Connect your computer to the same network as your rigs.
  2. Download Putty from http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe.
    Putty is an executable that can be run without installing.
  3. Find the IP of your rig.
    You can find your rig's IP on your ethosdistro.com stats panel, on your rig's desktop, or on your router's DHCP client table.
  4. Open Putty and input Rig Information.
    Type the rig's IP into Host Name. Port should be 22. Click Open.
  5. Login to ethOS.
    When the terminal window shows up, login with username ethos, password live.
  6. Begin using Linux.
    Type helpme and press ENTER to get started.

Pasting Text: In Windows, CTRL+C to copy text. In putty, SHIFT+INSERT to paste it.

To SSH remotely, change the root and ethos passwords, then set up SSH portforwarding on your router using the below guides:

You can also set up a dedicated VPN box on your rigs' network, and connect to it using your favorite VPN software.


Setting ethOS to single-rig mode

It is highly recommended that you use a remote config. However, if you only have one rig, you can turn on single-rig mode.

  1. Make the file /home/ethos/remote.conf completely blank.
    NOTE: this command will not return a confirmation, just copy and paste it:
    echo -n "" > /home/ethos/remote.conf

NOTE: If single-rig mode is not turned on, ethOS will over-write the contents of /home/ethos/local.conf.


Setting and Switching your Wallet and/or Pool

Note: If you have just one rig, set ethOS to single-rig mode before following this guide.

  1. Edit either your remotely hosted config file, or /home/ethos/local.conf (single-rig mode).
  2. Define your wallet and pools by replacing the default ones for proxywallet, proxypool1, proxypool2
  3. After you change the config, run putconf && minestop, the miner will stop, and then start up automatically with your new settings.
  4. Use show miner to watch the miner log.
  5. After your wallet is switched, in 5-10 minutes, your pool should show mining activity. You can copy and paste your wallet to the pool website interface in order to check for mining activity.

Using a Pool that requires workers, usernames, and passwords (suprnova)

Some pools (suprnova) require usernames, passwords, and workers. Follow this guide for configuring ethOS to work on these pools:

  1. Find your worker name for each rig. ethOS assigns a 6-digit alphanumeric code (worker name) for each rig.
    You can find out your worker name by looking at the ethosdistro.com stats panel, rig desktop, or ssh terminal.
  2. Login to the pool website. On the pool website, add a worker for each ethOS rig/worker that you have, use password "x".
    Note: If you use the loc parameter in your config, your worker name will be the loc that you specified.
  3. In your config, set proxywallet username where username is your actual pool-side user name that you use to login.
  4. After you change the config, run putconf && minestop, the miner will stop, and then start up automatically with your new settings.

Setting up your own remote config

  1. Copy http://ethosdistro.com/pool.txt and host it yourself on a remote server, vps, or shared hosting account that you control.
  2. Get the link to your remote config like http://your-server.com/config.txt.
    NOTE: The link http://your-server.com/config.txt is an example. You must use your own link.
  3. Import your remote config: echo -n "http://your-server.com/config.txt" > /home/ethos/remote.conf
  4. Make changes to your remotely hosted config, and reboot your rig to have them take effect.

After you set up your remote config, you can manage all your rigs via your remote config file, even remotely reboot them. More detailed configuration documentation is available at http://ethosdistro.com/pool.txt


Using ConfigMaker.com for your remote config

  1. Copy your config from /home/ethos/local.conf or from http://ethosdistro.com/pool.txt to the Text Editor at ConfigMaker.com
  2. Edit the config to suit your preferences and press 'Save Changes'.
  3. Bookmark your private text editor.
  4. Import your remote config to your ethOS rig: echo -n "https://configmaker.com/my/VeryNiceCleanConfig.txt" > /home/ethos/remote.conf
    NOTE: The link https://configmaker.com/my/VeryNiceCleanConfig.txt is an example. You must use your own link.
  5. Make changes to your ConfigMaker.com config, and reboot your rig to have them take effect.

Setting up a DigitalOcean droplet for your remote server

If you do not have a remote server, you can use DigitalOcean.

  1. Go to DigitalOcean (follow this link to get 2 months free), create an account, then click on "Create Droplet".
  2. Click on "One-Click Apps".
  3. Select "LAMP on 14.04", $5/mo, and the datacenter closest to your physical location.
  4. After the droplet is created, follow the SSH guide to SSH to your DigitalOcean droplet.
  5. Descend into the world-readable html directory with cd /var/www/html
  6. Copy the sample config to your DigitalOcean Droplet with wget http://ethosdistro.com/pool.txt
  7. Make changes to your remotely hosted config on your DigitalOcean droplet with nano /var/www/html/pool.txt
  8. The link to your remotely hosted config is now http://[your-digital-ocean-ip-address]/pool.txt
  9. To use your remote config, see: Setting up your own remote config.

Setting a static internal IP for your ethOS rig

In some cases, you may want to assign a static IP to your ethOS rig. It is recommended to assign static IPs based on mac addresses on your router. However, you can also set a static IP on linux itself:

  1. Make changes to your interfaces using this as a guide.
    in /etc/network/interfaces change:
    auto eth0
    iface eth0 inet dhcp
    to:
    auto eth0
    iface eth0 inet static
       address 192.168.0.201
       netmask 255.255.255.0
       network 192.168.0.0
       gateway 192.168.0.1
       dns-nameservers 8.8.8.8
    
  2. Reboot your rig.

NOTE: Set the IP according to your correct IP range, outside of your DHCP range.


Overclocking

It is best to have your rig stable for 24 hours before attempting overclocks.

  1. Follow the instructions on http://ethosdistro.com/pool.txt to set overclocks globally, or for individual rigs.
  2. After you set overclocks, you can either reboot, and the rig will take the new config and apply the new clocks automatically, or you can run putconf && ethos-overclock, and your rig will apply the overclocks during the mining session.
  3. Use show miner to watch the miner log.

NOTE: If your rig crashes or hangs after setting overclocks, follow the below instructions:

  1. Reduce all overclocks to stock settings and reboot.
  2. Monitor the rig for 24 hours to make sure it does not crash again.
  3. If required, set a less aggressive overclock and continue to monitor the rig.

Managing temperature

Your rig's GPUs will throttle (powertune set to 0 and core clock set to 800 mhz) if your GPU temperature reaches 5 degrees lower than maxgputemp in the config.

If you rig's GPUs overheat or throttle, follow the below suggestions for a permanent fix.

To reset all temperature-related conditions, you can reboot your rig or run clear-thermals


Setting a custom Panel ID

ethOS automatically assigns a 6-character panel ID based on a hash of your external IP address. This way, all rigs on one network can report to the same panel. If your public IP changes, your panel will change.

You can run helpme to get your current ethOS stats panel link.

You can set your own custom Panel ID with the custompanel parameter.

In your config, set custompanel publicsecret (exactly 12 characters) where public (exactly 6 characters) is your preferred panel ID, and secret (exactly 6 characters) is your private key. Then, reboot.

Example: custompanel myrigsrandom will make all your rigs report to http://myrigs.ethosdistro.com


Fixing unexpected low pool hashrate

The pool-side reported hashrate should be completely ignored. The pool reports may report a hashrate of "0", or of just a single GPU. Please use the pool-side effective hashrate to see your true hashrate for the entire rig.

If, after mining for 24 hours, your pool effective hashrate is unexpectedly low, follow the below instructions:

  1. Make sure that you are connecting to your pool via stratum.
    Do not use the pool config option if your node or pool is not on your local network, and make sure stratumproxy is enabled, and proxypool1 and proxypool2 are defined, as per the sample config located at http://ethosdistro.com/pool.txt.
  2. Ping your pool domain and make sure there is no packet loss (example: ping us1.ethermine.org)
    If there is packet loss, use another pool server that is closer to your geographic location.
  3. Reboot your rig.
  4. If you still get low hashrate, and if the router that your rig is connected to is also serving wifi, turn off the wifi feature and monitor the rig performance for another 24 hours.
  5. If the issue is resolved after disabling wifi, set up a dedicated router for your rig(s), and disable the wifi feature on the dedicated router.

Autotrading Altcoins for Bitcoin

You can autotrade your mined Altcoins directly to a Bitcoin Wallet.

  1. Go to https://shapeshift.io/
  2. Cick on the Deposit coin and select Ether (or any altcoin).
  3. Click on the Receive coin and select Bitcoin.
  4. Select Quick and click Continue.
  5. Input your Bitcoin Address and an Altcoin Refund Address (You can make an Ether Refund Address at myetherwallet.com)
  6. Checkmark I agree to terms and click Start Transaction.
  7. You will get a permanent receiving address. This address is controlled by Shapeshift, which will autotrade all deposits to Bitcoin, and send them to your Bitcoin Address.
  8. Set Shapeshift's receiving address in ethOS to mine directly to it and get Bitcoin in return.

Mining and Common Issues

Ethereum uses a DAG that is loaded into GPU VRAM. With every dag increase, hashrate lowers slightly. This is normal.

You can mine Expanse and other DaggerHashimoto coins simply by switching pools.

When some GPUs crash, you can sometimes determine which one is causing the crash by the GPUs memclock, which may downclock to 0.15ghz. This is visible in your ethosdistro.com stats panel.

The best powertune value for R9 290/x/390/x is 50.

The best core clock for R9 285/380 is 800mhz, which will reduce power and temperature usage with minimal effect on hashrate.

In most cases, adjusting gpu memory clock will result in instability. The best value is the default factory memory clock.


Provisioning AMD boards

If you have an AMD board and have network connectivity issues or are unable to successfully boot with multiple GPUs, follow the below instructions:

  1. If you have many GPUs, make sure that no GPU is plugged in directly to any 16x slot. Risers must be used for all GPUs.
  2. Unplug all GPUs except for gpu0 (ignore all 1x slots, gpu0 is always the 16x PCI-E slot physically closest to your motherboard's CPU socket).
  3. If your motherboard has molex or PCI-E onboard power jacks, make sure to plug the correct cable into them.
  4. Follow the instructions for Using a keyboard and monitor on ethOS.
  5. Boot your motherboard by shorting the power pins with a small metal tool (screwdriver).
  6. Upon boot, go into the motherboard bios and set the following options (set as many of these options as you can find):
    1. set BOOT ON POWER to ENABLE (enables rig to boot by flipping PSU Power Switch).
    2. set IOMMU to ENABLE.
    3. set VIRTUALIZATION (C1E) to DISABLE.
    4. set POWER CONTROL (SVM) to DISABLE.
    5. set CPU UNLOCK to ENABLE (this may prevent CPU temp from being read properly).
    6. set COOL AND QUIET to DISABLE.
    7. set CPU CORE CONTROL equal to the amount of CORES PER PROCESSOR for your particular CPU make/model.
    8. set ONBOARD AUDIO/SOUND to DISABLE.
    9. set IEEE1394 to DISABLE.
    10. set APU ONBOARD GRAPHICS to DISABLE.
  7. Save changes and reboot.
  8. Allow rig to boot completely with just one GPU, then update ethOS.
  9. After update, reboot, connect the rest of the GPUs.

Provisioning Intel boards

If you have an Intel board and have network connectivity issues or are unable to successfully boot with multiple GPUs, follow the below instructions:

  1. If you have many GPUs, make sure that no GPU is plugged in directly to any 16x slot. Risers must be used for all GPUs.
  2. Unplug all GPUs except for gpu0 (ignore all 1x slots, gpu0 is always the 16x PCI-E slot physically closest to your motherboard's CPU socket).
  3. If your motherboard has molex or PCI-E onboard power jacks, make sure to plug the correct cable into them.
  4. Follow the instructions for Using a keyboard and monitor on ethOS.
  5. Boot your motherboard by shorting the power pins with a small metal tool (screwdriver).
  6. Upon boot, go into the motherboard bios and set the following options (set as many of these options as you can find):
    1. set BOOT ON POWER to ENABLE (enables rig to boot by flipping PSU Power Switch).
    2. set VTd INTEL VIRTUALIZATION to DISABLE.
    3. set ONBOARD AUDIO/SOUND to DISABLE.
    4. set IEEE1394 to DISABLE.
    5. set ONBOARD GRAPHICS to DISABLE.
  7. Save changes and reboot.
  8. Allow rig to boot completely with just one GPU, then update ethOS.
  9. After update, reboot, connect the rest of the GPUs.

Fixing 290/390/470/480 boot problems with Intel boards

If you have an Intel board with running this GPU, you may experience boot problems in certain cases. Please see below for a list of fixes.

NOTE: If you use onboard video, POST will occur on onboard video, and the ethOS desktop will be displayed on gpu0.


Fixing ADL Error / Hardware Error

The following fatal errors will prevent mining if your GPU, RISER, or other HARDWARE experience a failure.

This hardware error cannot be fixed with software. Follow the procedure below to determine which hardware is causing the failure.

  1. Power off rig.
  2. Unplug half the GPUs from risers.
  3. Reseat the power and riser connections of the other half.
  4. Power rig back on.
  5. If the rig starts mining after step 4, proceed with step 6.
  6. Repeatedly add GPUs one by one until the rig experiences the above error again.
  7. If the rig does not start mining after step 4, then power off, unplug the other half, plug the other half back, and proceed with step 6.