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

Generating a Diagnostics Verkeersopstopping before joining #ethosdistro IRC Support
  1. Wait for your equipment to come in its crashed, violated, or non-working state.
  2. Connect to IRC with the below guides.
  3. Run gethelp ter a terminal while connected to your equipment, and copy/save the output verbinding.
  4. Paste the gethelp listig ter the support channel, describe the kwestie ter your own words, include latest switches and any troubleshooting steps that you have done.
  5. Wait for a reply and talk te channel.

Joining #ethosdistro IRC Support from your Web Browser
  1. On your regular PC or rekentuig, visit https://webchat.freenode.netwerk/?channels=ethosdistro.
  2. Come in a nickname for yourself.
  3. Do not switch 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.
Joining #ethosdistro IRC Support using your IRC Client
Joining #ethosdistro IRC Support from your local equipment
  1. Run ethoschat-local ter your ethOS terminal.
  2. Wait up to 15 seconds for your equipment to join the IRC channel.
  3. Altstem+Tabulator inbetween the regular Terminal and the ethoschat Terminal.
  4. Spil of ethOS 1.Three.0, you can run /gethelp directly ter the IRC talk window.
  5. To abandon ethoschat, run /uitgang inwards of the ethoschat Terminal and Altstem+Tabulator to the regular Terminal.
Joining #ethosdistro IRC Support from your remote equipment via SSH
  1. Run ethoschat ter your SSH session.
  2. Wait up to 15 seconds for your equipment to join the IRC channel.
  3. Spil of ethOS 1.Three.0, you can run /gethelp directly te the IRC talk window.
  4. To abandon ethoschat, run /uitgang inwards of your SSH session.

Quick Begin Guide

  1. Run helpme to get a list of directives, your stats panel listig, and equipment status.
  2. Force ethOS to keep local.conf switches after Reboots.
  3. Te /huis/ethos/local.conf , switch “0x0bdC4F12fB57d3acA9C3cF72B7AA2789A20d27f2” to your wallet (Editing Files with Nano).
  4. Switch both user “ethos” and superuser “root” password with passwd ethos and sudo passwd to secure your equipment.
  5. Reboot with r .

NOTE: If you would like to reset all configs to their factory defaults, use reset-config .

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

Common Directions on ethOS

Editing Files with Nano

All ethOS configuration is done by editing a configuration verkeersopstopping.

NOTE: To retrieve your wallet address, you can email it to yourself, then open the browser with browser and retreive it from your email.

Example usage for editing files with Nano:

  1. Open a opstopping with the nano text editor: nano /huis/ethos/local.conf
  2. Use the arrow keys on your keyboard to navigate around the text and delete the default wallet.
  3. Paste your own wallet with CTRL+V .
  4. Type CTRL+X , y , then press the Inject Key on your keyboard.

Movie Guides

  • General Movies
  • VirusHQ ethOS and Mining Movies
  • ethOS USB Mining System on BIOSTAR Crypto Mining Motherboard by BIOSTAR
  • Quick & Effortless Ethereum Mining Equipment Build with ethOS, article: ethos gpushack
  • Ultimate Mining Equipment – (180MH/s Ethereum, ZCash, Monero, and more), article: ultimate mining equipment
  • OMG a build, its bot to long by Pinnig Be Trippin’
  • Utter EthOS setup walkthrough 2018 by Pinnig Be Trippin’

Mining Zcash

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

Mining Monero

  1. Update ethOS.
  2. Get embarked with the Quick Commence Guide.
  3. Set globalminer sgminer-gm-xmr or miner [worker] sgminer-gm-xmr ter 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 voorwaarde be defined).
  6. If you have 2GB GPUs, set rawintensity to a lower value ter /huis/ethos/sgminer-gm-xmr.stub.conf
  7. If you practice crashing, revert to all stock clocks, check again, then revert to stock bios (roll GPU bios switch).
  8. If miner fails, eliminate both .WORKER from /huis/ethos/sgminer-gm-xmr.stub.conf (some pools do not accept worker well).

Updating ethOS to the Latest Version

  1. Read the changelog for very significant major switches.
  2. Become physicaly local to your equipments. Do not update remotely.
  3. Prior to updating, reboot your equipment (a fresh equipment is significant for a successful update).
  4. Instantly after your equipment boots successfully, run the update: sudo ethos-update && sleep Five && r (do not interrupt it)

NOTE: slow USB Two.0 drives may have trouble updating.

  • After your equipment updates, it will reboot. Observe your equipment come up.
  • If your equipment fails instantaneously after updating and rebooting, reupdate your equipment: sudo ethos-update reupdate && sleep Five && r
  • If reupdate fails, reimage to your supported Drive.
  • NOTE: For login download credentials, search your email for “gpushack”. Your username/pass are ter the email purchase confirmation.

  • Reply to any gpuShack email if you bought ethOS and have trouble downloading it.
  • Updating Miners to Latest Versions

    1. Update ethOS.
    2. Make sure your GPUs are not te a crashed state. It is best to proceed instantaneously after a reboot.
    3. Run: sudo update-miners && sudo service ethos-miner-monitor restart

    You can check your current miner versions with cat /var/run/ethos/miner.versions

    The following miners are presently available to update:

    • ccminer Two.Two.5-tpruvot-ethos6
    • claymore 11.6
    • claymore-xmr 11.Trio
    • claymore-zcash 12.6
    • dstm-zcash 0.6.0.1
    • ethminer 0.14.0.dev2
    • optiminer-zcash Two.1.Two
    • sgminer-gm Five.Five.6

    NOTE: If you have many equipments, use the above spil a guideline for your own distribution method.

    If any problem occurs and you would like to revert, run: ethos-update reupdate

    Installing Fixes on the Latest ethOS Version

    Thesis fixes vereiste ONLY be run on ethOS 1.Trio.0. Do not run thesis fixes if you are not affected by the problem that the fixes resolve.

    You can apply thesis fixes by copying and pasting the code text below into your ethOS terminal, then hitting the Inject key.

    • source Nvidia 390.25 Driver Installer

    Fixes issues associated with NVIDIA GTX 1060 6GB Rev2, NVIDIA GTX 1060 5GB, and NVIDIA Titan V.

    NOTE: Violates power usage display on NVIDIA GTX 1050Ti GPUs.

  • source Kernel Four.15-rc7 Installer
  • Fixes 511C / 0.0 hash error / system lockup that occurs upon ethOS startup on some fresh Gigabyte and MSI RX 570/580.

    Adds RX 550 support for mining.

    NOTE: Do not run on FGLRX R9/R7/HD or NVIDIA equipments.

  • sudo hotfix igpu-install and sudo hotfix igpu-uninstall iGPU Fixer
  • Permits iGPU to be used with more than 9 GPUs on AMDGPU (RX) equipments (uninstall option for users who do not use iGPU).

  • sudo hotfix amd-volt-fix Voltage Fixer
  • Fixes Voltages from config not applying to AMD RX GPUs.

    NOTE: Does not apply with the AMD Four.15-rc7 Kernel.

    Writing ethOS to an 8gb+ USB Trio.0 / HDD / SSD on Windows

    1. Download the ethOS verkeersopstopping (the ethOS opstopping is an archive that finishes te .xz).
    2. Samenvatting the downloaded archive with 7-zip, it will samenvatting into approximately a Five.0gb pic.

    NOTE: Do not use the native Windows unzip utility. If you use it, the downloaded archive will not samenvatting decently, and will be corrupted.

  • Do not climb on the verkeersopstopping. Use Raw Copy Implement (available at http://hddguru.com/software/HDD-Raw-Copy-Tool/ ).
  • Ass-plug te your USB or SSD Drive. If using an SSD, buttplug ter the destination SSD to the sata power cable very first, then to the sata gegevens cable. Do not use a USB Two.0 drive, it is too slow.
  • Raw Copy Instrument will recognize the drive and permit you to clone the ethOS .img onto the drive, sector for sector.
  • Writing ethOS to an 8gb+ USB Three.0 / HDD / SSD on Linux (debian/ubuntu flavors)

    1. Download and uncompress the downloaded opstopping with unxz /path/to/ethos.xz , it will samenvatting into approximately a Five.0gb photo.
    2. Confirm the location of your source ethOS .img verkeersopstopping:

    ls /path/to/ethos*.img

  • Ass-plug ter your USB or SSD Drive. If using an SSD, butt-plug te the destination SSD to the sata power cable very first, then to the sata gegevens cable. Do not use a USB Two.0 drive, it is too slow.
  • Confirm that your equipment sees your destination drive. You should see the destination drive emerge spil /dev/sdX where X is your enumerated drive (i.e. /dev/sdb):
  • fdisk -l | grep sd

  • Confirm that your destination drive is keurig with smartctl:
  • apt-get -fy install smartmontools

    smartctl -i /dev/sdX (substitute X with your enumeration)

  • Clone your source to your destination. VERY Significant, if you make a mistake and accidentally clone to a different drive, you will cause CATASTROPHIC Gegevens LOSS.
  • apt-get -fy install gddrescue

    ddrescue –force -r2 /path/to/ethos.img /dev/sdX (substitute X with your enumeration)

  • Observe the progress. ddrescue should finish with no errors. After it is done, it is safe to shutdown and power off your equipment. The ethOS drive is now ready for use.
  • Writing ethOS to an 8gb+ USB Trio.0 / HDD / SSD or SSD on OS X

    1. Ass-plug te your destination USB Drive. If using an SSD Drive, use a USB to SATA adapter. Do not use a USB Two.0 drive, it is too slow.
    2. Open “Disk Utility” (Zoeklicht -> search for “Disk Utility”) and select your outward Drive from the left sidebar, then click “Informatie” at the top.
    3. Note the device IDENTIFIER of the destination drive (it could be something like disk2 or disk3, it may vary).

    Significant: Selecting the wrong IDENTIFIER will cause catastrophic gegevens loss.

  • Select your destination drive and click “Unmount” at the top.
  • Download ethOS (.xz opstopping)
  • Open Terminal (Zoeklicht -> search for Terminal)
  • Type gunzip (note the space), then haul/druppel the downloaded .xz opstopping next to the space after gunzip
  • NOTE: Utter directive looks like gunzip /Users/YOURUSERNAME/Desktop/ethos-*.xz

  • Press the Come in key and wait for the extraction to finish.
  • Type sudo dd if= (no space after = ), then haul/druppel the extracted .img verkeersopstopping after sudo dd if= , then finish typing of=/dev/rIDENTIFIER bs=1m
  • NOTE: Utter guideline looks like sudo dd if=/Users/YOURUSERNAME/Desktop/ethos-*.img of=/dev/rIDENTIFIER bs=1m (note the r )

  • Press the Come in key and wait for the disk imaging process to accomplish.
  • When the process completes, you might get message omzichtig telling that the drive is not readable. Eject the drive at this point.
  • The ethOS drive is now ready for use.
  • Booting a Equipment without a Power Button

    Equipments do not need a power button. After this guide, you can use the I/O switch on the PSU to power the equipment on and off.

    1. Build your equipment spil if you were building a bench-test pc. Use the motherboard manual if necessary, and connect all components.
    2. Make sure your PSU is plugged te, and that the PSU switch is set to the ON position.
    3. Butt-plug te the RAM to the RAM slot(s) that are furthest away from the motherboard CPU socket (to avoid dual-channel RAM power cycling).
    4. Boot your motherboard by shorting the power pins with a puny metal instrument (screwdriver).
    5. Upon boot, go into the motherboard bios and set BOOT ON POWER to ENABLE or AC BACK ON (consultatie your manual).
    6. Save your settings, and uitgang.

    Initial Setup (using a Keyboard and Monitor on ethOS)

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

    1. Without using a riser, link a GPU to the gpu0 PCI-E slot on your motherboard. (overlook all 1x slots, the gpu0 PCI-E slot ter always the LONGEST 16x PCI-E slot that is physically closest to your motherboard’s CPU socket).
    2. Link your PSU 6/6+Two PCI-E power cable pins to the GPU PCI-E power cable jacks (located on the back of the GPU). All of the jacks vereiste have PCI-E power cables plugged te, there vereiste not be any empty jacks.
    3. Fasten a monitor to the left-most DVI port of gpu0. If you incorrectly connect your monitor to another GPU or to onboard movie, you will get a wit display.
    4. If your equipment POSTs, you will see a GPU detection screen during bootup. If your equipment does not Postbode, power off. Check to make sure the CPU, CPU cable, and 24-pin ATX cable are seated decently. Then, test each stick of RAM individually te each RAM slot.
    5. ethOS will boot to the desktop automatically. After your equipment boots successfully, all interaction with ethOS is done via the terminal screen.
    6. Once the ethOS desktop is displayed, you can power off and add more GPUs. Make sure to populate all long 16x PCI-E slots very first, and once they are all populated, only then you can populate the brief 1x PCI-E slots.

    If fewer GPUs demonstrate up here than are connected to your equipment, 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 directive will fix this.

    Booting into ethOS

    1. Liquidate all non-ethOS drives from your equipment.
    2. Cork the ethOS drive to your equipment. If using an SSD, cork te the SSD to the sata power cable very first, then to the sata gegevens cable.
    3. Boot the equipment.
    4. The equipment will boot to the ethOS desktop, and the ventilatoren will ramp up. The fan ramp-up is normal and is not indicative of a crash.

    NOTE! If your equipment gets stuck on rEFInd error, you vereiste set Quick BOOT to DISABLE te your motherboard bios.

    NOTE! If your equipment fails to boot due to “initramfs” error, EFI Shell, or boots directly to BIOS, proceed with the below guides:

    For USB Drives

    1. Power off your equipment.
    2. Ass-plug te your USB drive into one of the USB ports ter the same IO panel/hub spil the Ethernet Port, or into any USB Two.0 Port.
    3. If ethOS does not boot and shows efi_main() failed , switch motherboard BIOS boot order from:

    UEFI: usb : (NAME OF DRIVE) to USB: (NAME OF DRIVE) , i.e. switch from USB U to USB.

    For SSD Drives

    1. Power off your equipment.
    2. Attempt a few different SATA ports on your motherboard, some may be disabled ter BIOS.
    3. Attempt a different SATA power connection, it may not be seated decently.
    4. Attempt a different SATA gegevens cable, it may be faulty.

    If the punt is not resolved, reimage the drive from the ethOS download listig to your current drive, or a spare drive.

    If your equipment fails to boot due to “Kernel Fright”, reseat and test all RAM. Make sure that your equipment detects at least 4gb of RAM. If the kwestie persists, proceed with the below guides:

    Provisioning AMD boards

    If you have an AMD houtvezelplaat and have network connectivity issues or are incapable to successfully boot with numerous GPUs, go after the below guide:

    1. If you have many GPUs, make sure that no GPU is plugged ter directly to any 16x slot. Risers vereiste be used for all GPUs.
    2. Unplug all GPUs except for gpu0 (overlook 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 butt-plug the juist cable into them.
    4. Go after the guide for Initial Setup.
    5. Upon boot, go into the motherboard bios and set the following options (set spil many of thesis options spil you can find):
    • set IOMMU to ENABLE.
    • set VIRTUALIZATION (C1E) to DISABLE.
    • set POWER CONTROL (SVM) to DISABLE.
    • set CPU UNLOCK to ENABLE (this may prevent CPU temp from being read decently).
    • set COOL AND QUIET to DISABLE.
    • set CPU CORE CONTROL equal to the amount of CORES Vanaf PROCESSOR for your particular CPU make/prototype.
    • set ONBOARD AUDIO/SOUND (AZALIA) to DISABLE.
    • set IEEE1394 to DISABLE.
    • set APU ONBOARD GRAPHICS to DISABLE.
    • set CPU FREQUENCY SCALING to DISABLE.
    • set CPU Spectacle MODE to ENABLE.
    • set Rapid BOOT to DISABLE.
  • Save switches and reboot.
  • Permit equipment to boot totally with just one GPU, then update ethOS.
  • After update, reboot, connect the surplus of the GPUs.
  • Provisioning Intel boards

    If you have an Intel houtvezelplaat and have network connectivity issues or are incapable to successfully boot with numerous GPUs, go after the below guide:

    1. If you have many GPUs, make sure that no GPU is plugged ter directly to any 16x slot. Risers vereiste be used for all GPUs.
    2. Unplug all GPUs except for gpu0 (disregard 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 buttplug the onberispelijk cable into them.
    4. Go after the guide for Initial Setup.
    5. Upon boot, go into the motherboard bios and set the following options (set spil many of thesis options spil you can find):
    • set VTd INTEL VIRTUALIZATION to DISABLE.
    • set ONBOARD AUDIO/SOUND (AZALIA) to DISABLE.
    • set IEEE1394 to DISABLE.
    • set PCI-E SUBSYSTEM/LANES to x8/x4/x4
    • set ONBOARD GRAPHICS to DISABLE.
    • set PCI-E GENERATION to GEN2.
    • set CPU FREQUENCY SCALING to DISABLE.
    • set CPU Show MODE to ENABLE.
    • set Quick BOOT to DISABLE.
    • set CSM to ENABLE.
  • Save switches and reboot.
  • Permit equipment to boot entirely with just one GPU, then update ethOS.
  • After update, reboot, connect the surplus of the GPUs.
  • Decently distributing riser power to avoid instability

    GPUs use a loterijlot of power, and risers voorwaarde have power balanced decently. Equipments will crash and may never embark mining if they are not balanced.

    • You vereiste use 1 riser vanaf GPU, and GPUs voorwaarde not be plugged directly into the motherboard.
    • If possible, connect no more than 1 riser vanaf PSU cable.
    • Use PSU MOLEX connections when possible, no more than 1 riser vanaf MOLEX cable.
    • If you don’t have enough PSU MOLEX cables, use the RISER SATA adapter, and connect the riser to your PSU SATA cables.
    • Connect your risers to the MOLEX or SATA connector that is physically closest to your PSU opbergruimte, to reduce fever/resistance.
    • Do not connect any more than Two risers to any single MOLEX or SATA cable from your PSU.

    Fixing Kernel Scare with Five+ GPUs on Intel Z170/x/270/x/H110

    Go after the below guide if you have an Intel Z170/X/270/X/H110 motherboard and you practice problems booting with Five+ GPUs.

    1. Unplug all GPUs except one, and boot.
    2. If and only if you have an ethOS version under 1.Two.Two:
      • Update ethOS.
      • Significant: After updating and rebooting, wait for the ethOS desktop to display.
      • Once you are on the latest version of ethOS, run lga1151-flasher . After it says Successfully Installed Bios, power off your equipment.
      • Cork te all GPUs and boot into ethOS.

      For Unsupported Motherboards

      1. If the script comebacks No Bios Found, the ethOS support team will be notified automatically.
      2. Wait up to 24 hours for ethOS support team to add support for your Motherboard.
      3. Attempt to run lga1151-flasher again to resolve the punt.

      If you have a motherboard that is not supported by lga1151-flasher , you can also update your motherboard BIOS version to the latest manufacturer firmware by hand, yourself.

      Common BIOS Options for fixing Kernel Scare with Five+ GPUs

      All Motherboards
      • set CSM to ENABLE.
      • set Prompt BOOT to DISABLE.
      MSI Motherboards
      For ALL GPUs
      • Under “Windows OS Configuration” -> set WINDOWS 7 INSTALLATION MODE to DISABLE.
      • Under “Integrated Peripherals” -> set HD AUDIO CONTROLLER to DISABLE.
      • Set PCIE GEN to Wagen
      For RX Series GPUs (ter addition to ALL GPUs section)
      • Advanced Mode (F7) -> Settings -> Advanced Settings -> PCI-E Subsystem Settings -> set 4G DECODE to ENABLE.
      • set PEG1 to “GEN Two”
      • set PEG2 to “GEN Two”
      • set PCI Latency to “96 Cycles”
      For HD and R9 Series GPUs (te addition to ALL GPUs section)
      • Advanced Mode (F7) -> Settings -> Advanced Settings -> PCI-E Subsystem Settings -> set 4G DECODE to DISABLE.
      • set PEG1 to “GEN 1”
      • set PEG2 to “GEN 1”
      • set PCI Latency to “96 Cycles”
      ASUS Motherboards
      • Advanced mode (F7) -> “Boot” section -> set “4G Decode” to ENABLE.
      • Under “Advanced” -> Onboard Devices Configuration -> set HD AUDIO CONTROLLER to DISABLE.
      • Under “Advanced” -> PCH Configuration -> set PCI-E Listig Speed to GEN2.
      ASROCK Motherboards
      • Advanced -> Chipset settings -> switch TOLUD to Trio.5GB
      • Set all PCI-E settings to Automaat

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

      If you are running this GPU on an Intel motherboard, you may practice boot problems te certain cases. Please see the guide below:

      • Do not use this GPU ter the gpu0 slot. Instead, use another GPU.
      • Use a 16x16x ribbon riser ter the gpu0 slot.
      • Use onboard movie:
        1. set PRIMARY GRAPHICS to ONBOARD.
        2. set SHARE MEMORY to 32MB.

        NOTE: If you use onboard movie, Postbode will occur on onboard movie, 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 practice a failure.

        • hardware error: possible gpu/riser/power failure
        • hardware error, possible gpu/riser/power kwestie
        • adl_error
        • could not initialize adl interface
        • HARDWARE ERROR! POSSIBLE GPU / RISER / POWER Kwestie

        This hardware error cannot be immobile with software. Go after the proces below to determine which hardware is causing the failure.

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

        Sturdy Troubleshooting Guide for Motherboards and other Equipment Components

        Example: You suspect that your motherboard is faulty.

        Go after the below sturdy troubleshooting proces step-by-step and do not skip any steps. Failure to go after this guide when asked by ethOS or gpuShack staff (spil part of RMA proces) will result ter a voided warranty, spil described ter the gpuShack Warranty Agreement.

        This sturdy troubleshooting proces is useful because it isolates the kwestie to your suspect component. Otherwise, the kwestie could be a power balance kwestie, riser problem, liberate cabling, bad power socket, bad PSU, etc.

        Liquidate the motherboard from power and disconnect it from your equipment. Then, liquidate the CMOS battery for Ten minutes. After that, ass-plug the CMOS battery back ter and go after thesis guides: Booting a Equipment without a Power Button and Initial Setup. If the punt is unresolved, proceed with the below guides:

        IF YOU SUSPECT THAT YOUR MOTHERBOARD IS FAULTY, DO NOT Exchange Ter OTHER COMPONENTS INTO THE NON-WORKING Equipment Te THE HOPES THAT IT WILL WORK. INSTEAD, Interchange YOUR SUSPECT MOTHERBOARD INTO ANOTHER WORKING Equipment! THIS MEANS YOU Voorwaarde NOT TOUCH THE RAM, DRIVEs, CPUs, CABLEs, OR PSUs Te THE SUSPECT Equipment, AND THAT YOU Vereiste Eliminate ONLY THE MOTHEBOARD FROM THE SUSPECT Equipment.

        1. Find a working equipment.
        2. Power off the working equipment.
        3. Eliminate the suspect/”faulty” motherboard from your suspect/”faulty” equipment.
        4. Eliminate only the working motherboard from your working equipment, and keep the surplus of the components there.
        5. Exchange ter the suspect/”faulty” motherboard into the working equipment, where the previous working motherboard used to be.
        6. Test the working equipment and suspect motherboard by following thesis guides: Booting a Equipment without a Power Button and Initial Setup.

        If the punt is resolved, then the kwestie is not with the motherboard. You can do this process for any component that you suspect is faulty.

        Using SSH to Login to ethOS from Windows

        1. Connect your pc to the same network spil your equipments.
        2. Download Putty from http://the.earth.li/

        Putty is an executable that can be run without installing.

      • Find the IP of your equipment.
      • You can find your equipment’s IP on your ethosdistro.com stats panel, on your equipment’s desktop, or on your router’s DHCP client table.

      • Open Putty and input Equipment Information.
      • Type the equipment’s IP into Host Name. Port should be 22. Click Open.

      • Login to ethOS.
      • When the terminal window shows up, login with username ethos, password live.

      • Start using Linux.
      • Type helpme and press Come in to get commenced.

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

        To SSH remotely:

        You can also set up a dedicated VPN opbergruimte on your equipments’ network, and connect to it using your beloved VPN software.

        Force ethOS to keep local.conf switches after Reboots

        ethOS comes pre-installed with a sample remote config.

        It is very recommended that you use your own remote config. If you don’t want to use the remote config feature, you can turn it off with force-local

        ethOS will over-write the contents of /huis/ethos/local.conf if the remote config feature remains on.

        You can also wit out /huis/ethos/remote.conf to turn off the remote config feature.

        Setting and Switching your Wallet and/or Pool

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

        1. Edit either your remotely hosted config verkeersopstopping, or /huis/ethos/local.conf (single-rig mode).
        2. Define your wallet and pools by substituting the default ones for proxywallet , proxypool1 , proxypool2
        3. After you switch the config, run putconf && minestop , the miner will zekering, and then begin up automatically with your fresh settings.
        4. Use demonstrate miner to see the miner loom.
        5. After your wallet is switched, ter 5-10 minutes, your pool should demonstrate mining activity. You can copy and paste your wallet to the pool webstek interface te order to check for mining activity.

        Switching or removing your Worker Name

        To switch your worker name and assign a rack location, go after the below guide.

        1. Te your config, set loc [worker] newname ([worker] is your original 6-digit rigname and “newname” is your fresh equipment name).
        2. Do not add a newname to your wallet like wallet.newname, this will not work.
        3. Do not use very long newname. The maximum length is 8 characters.
        4. Do not use the same newname for numerous equipments.
        5. Reboot your equipment.

        After this proces, your pool will see your fresh worker name, and your equipment will have a fresh rack location assigned on the ethosdistro.com panel.

        Some pools do not support worker names. If you would like to eliminate your worker name, add globalname disabled or name [worker] disabled to your config.

        Using a Pool that Requires Workers, Usernames, and Passwords (suprnova)

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

        1. Find your worker name for each equipment. ethOS assigns a 6-digit alphanumeric code (worker name) for each equipment.

        You can find out your worker name by looking at the ethosdistro.com stats panel, equipment desktop, or ssh terminal.

      • Login to the pool webstek. On the pool webstek, add a worker for each ethOS equipment/worker that you have, use password “x”.
      • Note: If you use the loc parameter ter your config, your worker name will be the loc that you specified.

      • Ter your config, set proxywallet username where username is your actual pool-side user name that you use to login.
      • After you switch the config, run putconf && minestop , the miner will zekering, and then commence up automatically with your fresh settings.
      • Setting up your own Remote Config

        1. Copy http://ethosdistro.com/pool.txt and host it yourself on a remote server, vps, or collective hosting account that you control.
        2. Get the verbinding to your remote config like http://your-server.com/config.txt.

        NOTE: The verbinding http://your-server.com/config.txt is an example. You vereiste use your own verbinding.

      • Invoer your remote config: geluidsweerkaatsing -n “http://your-server.com/config.txt” > /huis/ethos/remote.conf
      • Make switches to your remotely hosted config, and reboot your equipment to have them take effect.
      • After you set up your remote config, you can manage all your equipments via your remote config verkeersopstopping, 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 /huis/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 Switches’.
        3. Bookmark your private text editor.
        4. Invoer your remote config to your ethOS equipment: weerklank -n “https://configmaker.com/my/VeryNiceCleanConfig.txt” > /huis/ethos/remote.conf

        NOTE: The listig https://configmaker.com/my/VeryNiceCleanConfig.txt is an example. You vereiste use your own verbinding.

      • Make switches to your ConfigMaker.com config, and reboot your equipment 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 (go after this verbinding to get Two months free), create an account, then click on “Create Droplet”.
        2. Click on “One-Click Apps”.
        3. Select “Verlichtingstoestel on 14.04”, $Five/mo, and the datacenter closest to your physical location.
        4. After the droplet is created, go after 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 switches to your remotely hosted config on your DigitalOcean droplet with nano /var/www/html/pool.txt
        8. The verbinding 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 Equipment

        Te some cases, you may want to assign a static IP to your ethOS equipment. 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 switches to your interfaces using this spil a guide.

        ter /etc/network/interfaces switch: to:

      • Reboot your equipment.
      • NOTE: Set the IP according to your onberispelijk IP range, outside of your DHCP range.

        Overclocking

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

        1. Go after the instructions on http://ethosdistro.com/pool.txt to set overclocks globally, or for individual equipments.
        2. After you set overclocks, you can either reboot, and the equipment will take the fresh config and apply the fresh clocks automatically, or you can run putconf && ethos-overclock , and your equipment will apply the overclocks during the mining session.
        3. Use demonstrate miner to witness the miner loom.

        NOTE: If your equipment crashes or strings up after setting overclocks, go after the below guide:

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

        Managing Temperature

        If your GPUs reach near the maxgputemp , all ventilatoren will set to 100%, and all GPUs will attempt to go into a lower power state.

        If your GPUs exceed maxgputemp , all mining programs will shut down.

        Go after the below steps to reduce the chances of your GPUs overheating:

        • Do not set fan speed on individual GPUs, set globalfan to a higher value.
        • Eliminate -tt from the claymore flags options, (using claymore fan control will pauze globalfan ).
        • Check to make sure there are no violated ventilatoren or liberate cables ter the GPU ventilatoren.
        • Budge the GPUs around ter your equipment, make sure that the best one has ample spacing for airflow.
        • Physically exchange the locations of the coldest and best GPUs te your equipment, to balance temperatures.
        • Set maxgputemp to a higher value.
        • Point a opbergruimte fan at your equipment, with the air flowing from the back of the GPU, out through the metal L-shaped IO brackets.
        • Repaste the GPU with thermal repaste, following the gpuShack repaste guide.

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

        Setting a Custom-made Panel ID

        ethOS automatically assigns a 6-character panel ID based on a hash of your outer IP address. This way, all equipments on one network can report to the same panel.

        If your public IP switches, your panel ID will switch. You can run helpme to get your current ethOS stats panel listig.

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

        • Ter your config, set custompanel publicsecret (EXACTLY 12 ALPHANUMERIC CHARACTERS!) and voorwaarde be the SAME code on all your equipments.
        • public (EXACTLY 6 ALPHANUMERIC CHARACTERS!) is your preferred panel ID.
        • secret (EXACTLY 6 ALPHANUMERIC CHARACTERS!) is your private key.
        • r to reboot.
        • Example Keurig usage: custompanel ethmanmg9490 will make all your equipments report to http://ethman.ethosdistro.com
        • Example INCORRECT usage: custompanel ethman will do nothing.

        Fixing Unexpected low Pool Hashrate

        The pool-side reported hashrate should be fully disregarded. 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 equipment.

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

        1. Make sure that you are connecting to your pool via stratum.

        Do not use the pool config option if your knot or pool is not on your local network, and make sure stratumproxy is enabled , and proxypool1 and proxypool2 are defined, spil vanaf the sample config located at http://ethosdistro.com/pool.txt.

      • 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.

      • Reboot your equipment.
      • If you still get low hashrate, and if the router that your equipment is connected to is also serving wifi, turn off the wifi feature and monitor the equipment spectacle for another 24 hours.
      • If the kwestie is resolved after disabling wifi, set up a dedicated router for your equipment(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.

        Related movie: Bitcoin Miner Software – Leaked Guide 2017


        No comments

        Leave a Reply

        Your email address will not be published. Required fields are marked *

        You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>