Home  ›  Ethos Download What Is the Best Os for Eth Mining

Ethos Download What Is the Best Os for Eth Mining

Edit

home · knowledge base of operations · pool · blog · changelog · source · statistics · support · sampleconf · ConfigMaker · buy ethOS · ASICseer

Table of Contents

Getting Support
Quick Start Guide
Editing Config with Nano
Editing Token with Nano
Common Commands on ethOS
Video Guides
Mining Zcash
Mining Monero
Increasing Hashrate on Tahiti/Tonga/Fiji GPUs with AMDGPU
Updating ethOS to the Latest Version
Updating Miners to Latest Versions
Installing Fixes on the Latest ethOS Version
Writing ethOS to an 8gb+ USB three.0 / HDD / SSD on Windows
Writing ethOS to an 8gb+ USB 3.0 / HDD / SSD on Linux (debian/ubuntu flavors)
Writing ethOS to an 8gb+ USB 3.0 / HDD / SSD or SSD on Bone X
Booting a Rig without a Power Button
Initial Setup (using a Keyboard and Monitor on ethOS)
Booting into ethOS
Provisioning AMD boards
Provisioning Intel boards
Properly distributing riser power to avoid instability
Fixing Kernel Panic with 5+ GPUs on Intel Z170/X/270/X/H110
Fixing 290/390/470/480 boot bug with Intel boards
Fixing ADL Error / Hardware Error
Robust Troubleshooting Guide for Motherboards and other Rig Components
Using SSH to Login to ethOS from Windows
Forcing ethOS to go on local.conf changes after Reboots
Setting and Switching your Wallet and/or Pool
Changing or removing your Worker Name
Using a Puddle that Requires Workers, Usernames, and Passwords (suprnova)
Setting upward 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 Console ID
Fixing Unexpected depression Pool Hashrate
Autotrading Altcoins for Bitcoin
Mining and Common Bug
Using TeamVIewer in ethOS

Getting Back up

At that place is no email or phone support for ethOS.

Support is bachelor 24/vii for ethOS customers who are compliant with the ethOS License Agreement. If you lot need back up, you must provide a gethelp Diagnostics File. Asking for support without providing it may result in a kicking or ban.

Generating a gethelp Diagnostics File before joining #ethosdistro IRC Support
  1. Connect to IRC with the beneath guides.
  2. Run gethelp in a terminal on your rig, and re-create/save the output link (you lot can also run /gethelp while inside the IRC channel).
  3. Paste the gethelp link in the support channel, draw the issue in your ain words, include contempo changes and any troubleshooting steps that y'all have washed.
  4. Wait for a reply and talk in channel.
Joining #ethosdistro IRC Support from your Web Browser
  1. On your regular PC or reckoner, visit http://ethosdistro.com/chat/?server=rizon
  2. Enter a nickname for yourself.
  3. Practice not change the "channels" field.
  4. Do not checkmark "auth to services".
  5. Checkmark "i'1000 not a robot".
  6. Click connect and expect up to 15 seconds to connect to the IRC channel.
Joining #ethosdistro IRC Support using your IRC Customer

Channel: #ethosdistro
Server: irc.ethosdistro.com
Port: 6667

Joining #ethosdistro IRC Support from your local rig
  1. Run ethoschat-local in your ethOS final.
  2. Expect up to xv seconds for your rig to join the IRC aqueduct.
  3. ALT+TAB between the regular Terminal and the ethoschat Terminal.
  4. As of ethOS one.3.0, y'all can run /gethelp direct in the IRC chat window.
  5. To quit ethoschat, run /exit within of the ethoschat Terminal and ALT+TAB to the regular Terminal.
Joining #ethosdistro IRC Support from your remote rig via SSH
  1. Run ethoschat in your SSH session.
  2. Wait upward to 15 seconds for your rig to join the IRC channel.
  3. As of ethOS one.3.0, you can run /gethelp directly in the IRC chat window.
  4. To quit ethoschat, run /get out 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. Force ethOS to go on local.conf changes after Reboots.
  3. In /home/ethos/local.conf , alter "0x0bdC4F12fB57d3acA9C3cF72B7AA2789A20d27f2" to your wallet (Editing Files with Nano).
  4. Modify both user "ethos" and superuser "root" password with passwd ethos and sudo passwd to secure your rig.
  5. Reboot with r.

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

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

Common Commands on ethOS

ethOS Command list and Common Answers: ♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦  Remote/Local Confs           /home/ethos/remote.conf  /dwelling/ethos/local.conf  Documentation / Sample Conf  ethosdistro.com/kb     ethosdistro.com/pool.txt   helpme:                show the list of common commands  allow/disallow:        allow OR disallow miner (automatic start)  minestop:              turn off all miner instances  show:                  show output of various log files  ww:                    show the ethOS desktop text in your terminal  dmesg:                 show brandish messages and commuter messages  r/hard-reboot:         issue a regular OR hard reboot   gethelp:               generate a diagnostics file for getting back up  df | pasteit:          send output of control (ex: df) to paste server  clear-thermals:        reset thermal-related throttling back to normal  force-local:           disable remote config  reset-config:          reset remote/local configuration dorsum to default  reset-network:         reset network configuration dorsum to default   update:                transport stats to stats console  putconf:               manually put remote conf into local conf  browser:               launch web browser on local rig  lock:                  lock the ethOS desktop   ethos-overclock:       force overclocks to use from local conf  ethos-update:          update ethOS to the latest version  restart-proxy:         restart local stratum proxy  ethos-readconf:        testify configuration variables (ex: validminers)  ethos-driver on/off:   turn on/off graphics driver for the adjacent boot  ethoschat:             help conversation (in current terminal session)  ethoschat-local:       help conversation (on rig, in separate window)  find-gpu:              example: find-gpu ane     (revs gpu1 fan up/downward)  sudo atiflash:         flashing utility for AMD GPUs  lga1151-flasher:       see ethosdistro.com/Grand  update-miner(s):       updates all miner programs to latest versions ♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦

Editing Config with Nano

All ethOS configuration is washed by editing a configuration file.

NOTE: To recollect your wallet accost, you lot tin can e-mail 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 file with the nano text editor: nano /habitation/ethos/local.conf
  2. Apply the arrow keys on your keyboard to navigate effectually the text and delete the default wallet.
  3. Paste your own wallet with CTRL+5.
  4. Type CTRL+X, y, so printing the Enter Key on your keyboard.

Editing Token with Nano

  1. Re-create your token from your gpuShack business relationship with CTRL+C.
  2. Open up your token file with the nano text editor: nano /abode/ethos/token.auth
  3. Paste your token into the file with CTRL+V or SHIFT+INSERT (depending on your terminal).
  4. Type CTRL+X, y, then printing the Enter Key on your keyboard.

You lot can also import your token by running: repeat -north "YOUR.TOKEN" > /home/ethos/token.auth

If y'all take trouble, watch the EthOSdistro Panel Authentication Walkthrough.

Video Guides

  • General Videos
  • EthOSdistro Panel Authentication Walkthrough
  • VirusHQ ethOS and Mining Videos
  • ethOS USB Mining Arrangement on BIOSTAR Crypto Mining Motherboard by BIOSTAR
  • Quick & Easy Ethereum Mining Rig Build with ethOS, article: ethos gpushack
  • Ultimate Mining Rig - (180MH/south Ethereum, ZCash, Monero, and more), article: ultimate mining rig
  • OMG a build, its been to long past Bits Be Trippin'
  • Total EthOS setup walkthrough 2017 by Bits Be Trippin'

Mining Zcash

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

Mining Monero

  1. Update ethOS.
  2. Become started with the Quick Start Guide.
  3. Run sudo update-miner xmr-stak
  4. Set globalminer xmr-stak or miner [worker] xmr-stak in config.
  5. Set proxywallet to your Monero wallet. Notation: If mining to exchange, you need proxywallet wallet.paymentid
  6. Set proxypool1 and proxypool2 to your Monero pools (both pools must be defined).

If you experience issues with Mining Monero:

  • If yous receive a Retention ALLOC FAILED: mmap failed error, run sudo hotfix install-xmr-memfix
    (to remove, sudo hotfix remove-xmr-memfix).
  • If you feel crashing, revert to all stock clocks, check again, then revert to stock bios (flip GPU bios switch).
  • Some pools practice not support worker names. If you would like to remove your worker name, add together globalname disabled or proper noun [worker] disabled to your config.

Dual miner threading with xmr-stak

NOTE: FOR ADVANCED USERS ONLY!

  1. Add --amd /home/ethos/xmr-stak-amd.stub.conf to the finish of your xmr-stak=flags line in your config.
  2. Run minestop && sleep 5 && minestart
  3. The in a higher place two steps have now generated xmr-stak-amd.stub.conf
  4. Edit the newly created stub file with nano xmr-stak-amd.stub.conf using the dual-thread documentation as a guide.
  5. Salvage and run minestop to apply.

For more than information on how to use this configuration file, refer to fireice-uk's tuning guide.

To get max hashrate, see https://www.youtube.com/watch?v=4FK3rY4WtsE

Increasing Hashrate on Tahiti/Tonga/Republic of the fiji islands GPUs with AMDGPU

Mining ethash on 3GB GPUs requires at least ethOS 1.3.3 and Claymore 12 to run correctly.

As of ethOS ane.iii.iii, yous tin can increase the hashrate of older GPUs (Tahiti/Tonga/Fiji Serial) by switching the driver from fglrx to amdgpu.

  • List of Tahiti GPUs
  • List of Tonga GPus
  • List of Fiji GPUs

Note! If you practise non have whatsoever of the above GPUs, Practise Not PROCEED with the beneath guide. Please also note that most hashrate improvements are limited to ethash mining.

Follow the below instructions to set your driver to amdgpu.

  1. In your config, set legacydriver [worker] amdgpu / globallegacydriver amdgpu
  2. Then, fix miner [worker] claymore-legacy or globalminer claymore-legacy
  3. Run: putconf && sleep 30 && r
  4. Afterwards you lot rig reboots, your Tahiti, Tonga, and Fiji GPUs will have an increased hashrate.

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. Prior to updating, reboot your rig (a fresh rig is important for a successful update).
  4. Immediately after your rig boots successfully, run the update: sudo ethos-update && sleep 5 && sudo reboot (do not interrupt it)
    Notation: slow USB ii.0 drives may have trouble updating.
  5. After your rig updates, it will reboot. Scout your rig come up upwardly.

If you experience bug with updating, encounter below:

  1. If your rig fails immediately afterward updating and rebooting, reupdate your rig: sudo ethos-update reupdate && slumber 5 && sudo reboot
  2. If you accept trouble with the updater itself, you tin can repair it with sudo repair-ethos-update. Then, yous can rerun it with sudo ethos-update reupdate && sleep 5 && reboot
  3. If reupdate fails, reimage to your supported bulldoze.
  4. If y'all bought ethOS, and you don't have your download instructions, please see these instructions.

Updating Miners to Latest Versions

  1. Update ethOS.
  2. Make certain your GPUs are not in a crashed country. It is best to go on immediately later on a reboot.
  3. Run: sudo update-miners && sudo service ethos-miner-monitor restart

Note: You tin can likewise update a unmarried miner like update-miner sgminer-gm

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

NOTE: If you have many rigs, utilize the above as a guideline for your ain distribution method.
If whatsoever problem occurs and yous would similar to revert, run: ethos-update reupdate

Installing Fixes on the Latest ethOS Version

These fixes must Merely be run on ethOS i.3.one. Practice not run these fixes if you are not affected by the problem that the fixes resolve.

You can utilize these fixes by copying and pasting the code text beneath into your ethOS terminal, then striking the Enter key.

  • sudo install-nv-betaNvidia 390.25 Commuter Installer
    Fixes problems associated with NVIDIA GTX 1060 6GB Rev2, NVIDIA GTX 1060 5GB, and NVIDIA Titan V.
    Note: Breaks power usage display on NVIDIA GTX 1050Ti GPUs.
  • sudo hotfix igpu-install and sudo hotfix igpu-uninstalliGPU Fixer
    Allows iGPU to be used with more than 9 GPUs on AMDGPU (RX) rigs (uninstall option for users who do not use iGPU).
  • sudo hotfix 1080hashupInstalls OhGodACompany's EthLargement and enables on boot
    Enhances 1080 / 1080 TI / Titan XP hash rate on Ethereum and potential other algorithms.
    Note: May be enabled / disabled using the following commands once installed:
    Enable: sudo hotfix enable-1080hashup
    Disable: sudo hotfix disable-1080hashup

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

Follow the beneath process discussion-for-give-and-take and do non skip any steps in order to successfully write ethOS to your boot media.

  1. Download the ethOS file (the ethOS file is an archive that ends in .xz).
  2. Extract the downloaded archive with seven-zip, it will excerpt into approximately a five.0gb epitome.
    NOTE: Exercise not use the native Windows unzip utility. If you apply information technology, the downloaded archive will not excerpt properly, and will be corrupted.
  3. Do not mountain the file. Use Raw Copy Tool (available at http://hddguru.com/software/HDD-Raw-Copy-Tool/ ).
  4. Plug in your USB or SSD Bulldoze. If using an SSD, plug in the destination SSD to the sata power cable first, so to the sata data cable. Do not use a USB 2.0 bulldoze, information technology is too slow.
  5. Raw Copy Tool volition recognize the drive and permit you to clone the ethOS .img onto the bulldoze, sector for sector.

Writing ethOS to an 8gb+ USB iii.0 / HDD / SSD on Linux (debian/ubuntu flavors)

  1. Download and uncompress the downloaded file with unxz /path/to/ethos.xz, it will extract into approximately a five.0gb image.
  2. Confirm the location of your source ethOS .img file:
    ls /path/to/ethos*.img
  3. Plug in your USB or SSD Drive. If using an SSD, plug in the destination SSD to the sata power cable first, then to the sata data cablevision. Practice non utilize a USB 2.0 drive, it is also slow.
  4. Confirm that your rig sees your destination drive. You should see the destination bulldoze appear as /dev/sdX where Ten is your enumerated drive (i.east. /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 volition crusade CATASTROPHIC Information LOSS.
    apt-become -fy install gddrescue
    ddrescue --forcefulness -r2 /path/to/ethos.img /dev/sdX (supercede X with your enumeration)
  7. Spotter the progress. ddrescue should cease with no errors. After it is done, it is condom to shutdown and power off your rig. The ethOS bulldoze is now fix for utilise.

Writing ethOS to an 8gb+ USB 3.0 / HDD / SSD or SSD on OS X

  1. Plug in your destination USB Drive. If using an SSD Drive, use a USB to SATA adapter. Practice not utilize a USB two.0 drive, it is too irksome.
  2. Open up "Deejay Utility" (Spotlight -> search for "Disk Utility") and select your external Drive from the left sidebar, so click "Info" at the top.
  3. Note the device IDENTIFIER of the destination drive (information technology could be something like disk2 or disk3, it may vary).
    Of import: Selecting the wrong IDENTIFIER will cause catastrophic data loss.
  4. Select your destination drive and click "Unmount" at the meridian.
  5. Download ethOS (.xz file)
  6. Open up Final (Spotlight -> search for Terminal)
  7. Type sudo gunzip (note the space), so elevate/drop the downloaded .xz file adjacent to the space after gunzip
    Annotation: Full control looks like sudo gunzip /Users/YOURUSERNAME/Desktop/ethos-*.xz
  8. Press the Enter key and wait for the extraction to complete.
  9. Type sudo dd if= (no space after =), then drag/drib the extracted .img file after sudo dd if=, then finish typing of=/dev/rIDENTIFIER bs=1m
    Notation: Full command looks like sudo dd if=/Users/YOURUSERNAME/Desktop/ethos-*.img of=/dev/rIDENTIFIER bs=1m (note the r)
  10. Press the Enter cardinal and look for the deejay imaging process to consummate.
  11. When the process completes, y'all might get message warning saying that the drive is non readable. Eject the drive at this signal.
  12. The ethOS drive is now ready for employ.

Booting a Rig without a Power Button

Rigs practise non need a ability button. Subsequently this guide, you can utilize the I/O switch on the PSU to ability the rig on and off.

  1. Build your rig as if you were building a bench-test calculator. Use the motherboard manual if necessary, and connect all components.
  2. Make sure your PSU is plugged in, and that the PSU switch is set to the ON position.
  3. Plug in the RAM to the RAM slot(due south) that are furthest away from the motherboard CPU socket (to avoid dual-channel RAM power cycling).
  4. Boot your motherboard by shorting the ability pins with a small metal tool (screwdriver).
  5. Upon boot, go into the motherboard bios and set Kick ON Power to ENABLE or AC BACK ON (consult your manual).
  6. Save your settings, and exit.

Initial Setup (using a Keyboard and Monitor on ethOS)

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

  1. Without using a riser, attach a GPU to the gpu0 PCI-Due east slot on your motherboard. (ignore all 1x slots, the gpu0 PCI-E slot in always the LONGEST 16x PCI-E slot that is physically closest to your motherboard's CPU socket).
  2. Attach your PSU 6/half-dozen+2 PCI-Due east power cablevision pins to the GPU PCI-E ability cable jacks (located on the back of the GPU). All of the jacks must have PCI-E power cables plugged in, at that place must not be any empty jacks.
  3. Attach a monitor to the left-most DVI port of gpu0. If you lot incorrectly connect your monitor to some other GPU or to onboard video, you will get a blank display.
  4. If your rig POSTs, y'all will meet a GPU detection screen during bootup. If your rig does not Post, power off. Bank check to make sure the CPU, CPU cablevision, and 24-pin ATX cable are seated properly. Then, examination each stick of RAM individually in each RAM slot.
  5. ethOS will kicking to the desktop automatically. Afterwards your rig 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 together more GPUs. Make sure to populate all long 16x PCI-East slots first, and in one case they are all populated, only then you can populate the short 1x PCI-E slots.

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

Booting into ethOS

  1. Remove all non-ethOS drives from your rig.
  2. Plug the ethOS bulldoze to your rig. If using an SSD, plug in the SSD to the sata power cable first, and then to the sata information cable.
  3. Boot the rig.
  4. The rig will boot to the ethOS desktop, and the fans volition ramp up. The fan ramp-up is normal and is non indicative of a crash.

Annotation! If your rig gets stuck on rEFInd error, you must set FAST BOOT to DISABLE in your motherboard bios.
Annotation! If your rig fails to kicking due to initramfs error, EFI Shell error, /dev/disk/... does not exist error, or boots directly to BIOS, proceed with the below guides:

For USB Drives

  1. Power off your rig.
  2. Plug in your USB drive into one of the USB ports in the same IO panel/hub as the Ethernet Port, or into whatever USB ii.0 Port.
  3. If ethOS does not boot and shows efi_main() failed, change motherboard BIOS boot social club from:
    UEFI: usb : (NAME OF Drive) to USB: (NAME OF Bulldoze), i.e. change from USBU to USB .

For SSD Drives

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

If the issue is not resolved, reimage the bulldoze from the ethOS download link to your current drive, or a spare bulldoze.

If your rig fails to boot due to "Kernel Panic", reseat and test all RAM. Make certain that your rig detects at least 4gb of RAM. If the issue persists, continue with the below guides:

Provisioning AMD boards

If y'all have an AMD board and take network connectivity issues or are unable to successfully kicking with multiple GPUs, follow the below guide:

  1. If you have many GPUs, brand sure that no GPU is plugged in directly to any 16x slot. Risers must exist 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. If your motherboard has two ethernet ports, disable one of them in the BIOS.
  5. Follow the guide for Initial Setup.
  6. Upon boot, go into the motherboard bios and gear up the post-obit options (gear up as many of these options as you tin can detect):
    • set IOMMU to ENABLE.
    • set up VIRTUALIZATION (C1E) to DISABLE.
    • set up POWER Control (SVM) to DISABLE.
    • set CPU UNLOCK to ENABLE (this may prevent CPU temp from beingness read properly).
    • set Cool AND QUIET to DISABLE.
    • fix CPU CORE CONTROL equal to the amount of CORES PER PROCESSOR for your particular CPU make/model.
    • set ONBOARD Sound/Audio (AZALIA) to DISABLE.
    • set up IEEE1394 to DISABLE.
    • prepare APU ONBOARD GRAPHICS to DISABLE.
    • set CPU FREQUENCY SCALING to DISABLE.
    • prepare CPU Performance Style to ENABLE.
    • set up FAST BOOT to DISABLE.
  7. Relieve changes and reboot.
  8. Allow rig to boot completely with merely 1 GPU, then update ethOS.
  9. Later on update, reboot, connect the rest of the GPUs.

Provisioning Intel boards

If y'all have an Intel board and have network connectivity issues or are unable to successfully boot with multiple GPUs, follow the below guide:

  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 e'er the 16x PCI-East slot physically closest to your motherboard's CPU socket).
  3. If your motherboard has molex or PCI-East onboard power jacks, make sure to plug the right cable into them.
  4. If your motherboard has ii ethernet ports, disable one of them in the BIOS.
  5. Follow the guide for Initial Setup.
  6. Upon boot, go into the motherboard bios and gear up the following options (set every bit many of these options as you lot can notice):
    • set VTd INTEL VIRTUALIZATION to DISABLE.
    • set ONBOARD Sound/SOUND (AZALIA) to DISABLE.
    • ready IEEE1394 to DISABLE.
    • set PCI-E SUBSYSTEM/LANES to x8/x4/x4
    • set up ONBOARD GRAPHICS to DISABLE.
    • ready PCI-E GENERATION to GEN2.
    • ready CPU FREQUENCY SCALING to DISABLE.
    • set CPU PERFORMANCE MODE to ENABLE.
    • fix FAST BOOT to DISABLE.
    • set CSM to ENABLE.
  7. Salvage changes and reboot.
  8. Permit rig to kick completely with merely ane GPU, then update ethOS.
  9. After update, reboot, connect the rest of the GPUs.

Properly distributing riser power to avoid instability

GPUs use a lot of power, and risers must take power balanced properly. Rigs volition crash and may never commencement mining if they are non balanced.

  • Y'all must use 1 riser per GPU, and GPUs must not be plugged directly into the motherboard.
  • If possible, connect no more 1 riser per PSU cable.
  • Use PSU MOLEX connections when possible, no more than 1 riser per MOLEX cablevision.
  • If you don't have plenty 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 box, to reduce oestrus/resistance.
  • Exercise not connect any more than 2 risers to whatsoever single MOLEX or SATA cable from your PSU.

Fixing Kernel Panic with v+ GPUs on Intel Z170/x/270/x/H110

Follow the below guide if y'all accept an Intel Z170/10/270/X/H110 motherboard and you feel bug booting with 5+ GPUs.

  1. Unplug all GPUs except one, and boot.
  2. Update ethOS.
  3. Once you are on the latest version of ethOS, run lga1151-flasher. Subsequently it says Successfully Installed Bios, power off your rig.
  4. Plug in all GPUs and boot into ethOS.

For Unsupported Motherboards

  1. If the script returns No Bios Found, the ethOS support team volition exist notified automatically.
  2. Expect up to 24 hours for ethOS back up team to add together support for your Motherboard.
  3. Attempt to run lga1151-flasher again to resolve the issue.

If y'all have a motherboard that is non supported by lga1151-flasher, you tin can also update your motherboard BIOS version to the latest manufacturer firmware manually, yourself.

Common BIOS Options for fixing Kernel Panic with 5+ GPUs

All Motherboards
  • gear up CSM to ENABLE.
  • set FAST BOOT to DISABLE.
MSI Motherboards
For ALL GPUs
  • Under "Windows OS Configuration" -> set WINDOWS 7 INSTALLATION MODE to DISABLE.
  • Nether "Integrated Peripherals" -> set Hd AUDIO CONTROLLER to DISABLE.
  • Ready PCIE GEN to Motorcar
For RX Series GPUs (in addition to ALL GPUs section)
  • Advanced Mode (F7) -> Settings -> Avant-garde Settings -> PCI-E Subsystem Settings -> set 4G DECODE to ENABLE.
  • set PEG1 to "GEN two"
  • set PEG2 to "GEN 2"
  • ready PCI Latency to "96 Cycles"
For Hard disk and R9 Serial GPUs (in addition to ALL GPUs department)
  • Avant-garde Mode (F7) -> Settings -> Advanced Settings -> PCI-Eastward Subsystem Settings -> set 4G DECODE to DISABLE.
  • set PEG1 to "GEN 1"
  • set PEG2 to "GEN i"
  • set PCI Latency to "96 Cycles"
ASUS Motherboards
  • Advanced mode (F7) -> "Kicking" section -> set "4G Decode" to ENABLE.
  • Under "Avant-garde" -> Onboard Devices Configuration -> set HD AUDIO CONTROLLER to DISABLE.
  • Under "Avant-garde" -> PCH Configuration -> fix PCI-E Link Speed to GEN2.
ASROCK Motherboards
  • Avant-garde -> Chipset settings -> modify TOLUD to 3.5GB
  • Gear up all PCI-Due east settings to AUTO

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

If you are running this GPU on an Intel motherboard, you may experience kick problems in certain cases. Delight see the guide beneath:

  • Do not employ this GPU in the gpu0 slot. Instead, utilise another GPU.
  • Use a 16x16x ribbon riser in the gpu0 slot.
  • Use onboard video:
    1. set Main GRAPHICS to ONBOARD.
    2. set up SHARE MEMORY to 32MB.

NOTE: If yous use onboard video, Mail service will occur on onboard video, and the ethOS desktop will be displayed on gpu0.

Fixing ADL Error / Hardware Error

The post-obit fatal errors volition prevent mining if your GPU, RISER, or other HARDWARE feel a failure.

  • hardware fault: possible gpu/riser/ability failure
  • hardware error, possible gpu/riser/power outcome
  • adl_error
  • could not initialize adl interface
  • HARDWARE Error! POSSIBLE GPU / RISER / Power ISSUE

This hardware mistake cannot be stock-still with software. Follow the procedure below to determine which hardware is causing the failure.

  1. Ability off rig.
  2. Unplug one-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 footstep 4, proceed with footstep 6.
  6. Repeatedly add GPUs ane by one until the rig experiences the above error again.
  7. If the rig does non start mining after step 4, then power off, unplug the other half, plug the other half dorsum, and proceed with step 6.

Robust Troubleshooting Guide for Motherboards and other Rig Components

Example: You suspect that your motherboard is faulty.

Follow the below robust troubleshooting procedure footstep-by-step and do not skip any steps. Failure to follow this guide when asked past ethOS or gpuShack staff (as part of RMA procedure) will effect in a voided warranty, equally described in the gpuShack Warranty Understanding.

This robust troubleshooting procedure is useful considering it isolates the issue to your suspect component. Otherwise, the consequence could be a power balance issue, riser problem, loose cabling, bad ability socket, bad PSU, etc.

Remove the motherboard from power and disconnect it from your rig. Then, remove the CMOS bombardment for 10 minutes. Later on that, plug the CMOS battery back in and follow these guides: Booting a Rig without a Power Push and Initial Setup. If the upshot is unresolved, continue with the below guides:

IF You lot Doubtable THAT YOUR MOTHERBOARD IS FAULTY, DO Non Swap IN OTHER COMPONENTS INTO THE Not-WORKING RIG IN THE HOPES THAT IT WILL Piece of work. INSTEAD, SWAP YOUR SUSPECT MOTHERBOARD INTO Some other WORKING RIG! THIS MEANS YOU MUST Not MOVE THE RAM, DRIVEs, CPUs, CABLEs, OR PSUs FROM THE Doubtable RIG, AND THAT YOU MUST REMOVE ONLY THE MOTHERBOARD FROM THE Doubtable RIG.

  1. Notice a working rig.
  2. Ability off the working rig.
  3. Remove the suspect/"faulty" motherboard from your doubtable/"faulty" rig.
  4. Remove only the working motherboard from your working rig, and proceed the rest of the components in that location.
  5. Bandy in the doubtable/"faulty" motherboard into the working rig, where the previous working motherboard used to exist.
  6. Test the working rig and suspect motherboard by following these guides: Booting a Rig without a Power Button and Initial Setup.

If the issue is resolved, then the issue is not with the motherboard. You can do this procedure for whatever component that you suspect is faulty.

Using SSH to Login to ethOS from Windows

  1. Connect your calculator to the same network equally your rigs.
  2. Download Putty from http://the.world.li/~sgtatham/putty/latest/x86/putty.exe.
    Putty is an executable that can be run without installing.
  3. Detect the IP of your rig.
    You can find your rig's IP on your ethosdistro.com stats panel, on your rig'due south desktop, or on your router's DHCP customer tabular array.
  4. Open Putty and input Rig Information.
    Blazon the rig'southward IP into Host Name. Port should be 22. Click Open.
  5. Login to ethOS.
    When the terminal window shows upwards, login with username ethos, password alive.
  6. Begin using Linux.
    Blazon 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:

  1. Change the root and ethos passwords. NOTE: Failure to modify passwords volition allow people to hack your ethOS (loftier rx/tx).
  2. Set up SSH portforwarding on your router using the below guides:
  • http://askubuntu.com/questions/423942/change-countersign-on-root-user-and-user-account
  • https://world wide web.google.com/search?q=ssh%20port%20forwarding

You tin can likewise set upwardly a defended VPN box on your rigs' network, and connect to it using your favorite VPN software.

Forcefulness ethOS to proceed local.conf changes after Reboots

ethOS comes pre-installed with a sample remote config.

Information technology is highly recommended that you use your ain remote config. If yous don't want to utilize the remote config feature, you lot can turn information technology off with force-local

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

You can also blank out /home/ethos/remote.conf to plough off the remote config feature.

Setting and Switching your Wallet and/or Pool

Note: If yous 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 past replacing the default ones for proxywallet, proxypool1, proxypool2
  3. Subsequently you change the config, run putconf && minestop, the miner volition stop, and then beginning up automatically with your new settings.
  4. Use bear witness miner to watch the miner log.
  5. After your wallet is switched, in five-10 minutes, your puddle should prove mining activity. You can re-create and paste your wallet to the pool website interface in guild to bank check for mining action.

Changing or removing your Worker Name

To switch your worker proper noun and assign a rack location, follow the below guide.

  1. In your config, set loc [worker] newname ([worker] is your original 6-digit rigname and "newname" is your new rig name).
  2. Do not add a newname to your wallet like wallet.newname, this will non work.
  3. Do not use very long newname. The maximum length is viii characters.
  4. Do non use the same newname for multiple rigs.
  5. Reboot your rig.

Later on this procedure, your pool will meet your new worker name, and your rig will have a new rack location assigned on the ethosdistro.com panel.

Some pools do non support worker names. If you lot would like to remove your worker proper name, add together globalname disabled or proper noun [worker] disabled to your config.

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. Observe your worker name for each rig. ethOS assigns a 6-digit alphanumeric code (worker proper noun) for each rig.
    You tin find out your worker name by looking at the ethosdistro.com stats panel, rig desktop, or ssh terminal.
  2. Login to the puddle website. On the puddle website, add together a worker for each ethOS rig/worker that you have, employ countersign "x".
    Note: If you use the loc parameter in your config, your worker name will be the loc that y'all specified.
  3. In your config, prepare proxywallet username where username is your bodily pool-side user proper noun that yous use to login.
  4. After y'all alter the config, run putconf && minestop, the miner will finish, so start upward automatically with your new settings.

Setting upwardly your own Remote Config

  1. Copy http://ethosdistro.com/pool.txt and host information technology yourself on a remote server, vps, or shared hosting account that yous command.
  2. Go 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 utilise your own link.
  3. Import your remote config: echo -n "http://your-server.com/config.txt" > /dwelling house/ethos/remote.conf
  4. Make changes to your remotely hosted config, and reboot your rig to have them take result.

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

Using ConfigMaker.com for your Remote Config

  1. Go to ConfigMaker.com
  2. Set your custompanel (optional, only recommended), edit the config to suit your preferences.
  3. Press 'Save Changes' and bookmark your individual text editor.
  4. Make changes to your ConfigMaker.com config to manage your rigs.

Setting up your ConfigMaker config allows you to manage all of your rigs remotely (even reboot).

Setting upwardly a DigitalOcean Droplet for your Remote Server

If yous do not have a remote server, you lot tin utilize DigitalOcean.

  1. Get to DigitalOcean (follow this link to get 2 months complimentary), create an account, so click on "Create Droplet".
  2. Click on "1-Click Apps".
  3. Select "LAMP on 14.04", $5/mo, and the datacenter closest to your physical location.
  4. Subsequently 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/puddle.txt
  7. Brand 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 employ your remote config, run across: 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. Information technology is recommended to assign static IPs based on mac addresses on your router. However, you lot can also set a static IP on linux itself:

  1. Make changes to your interfaces using this equally 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.ane    dns-nameservers viii.eight.8.8
  2. Reboot your rig.

Notation: Ready the IP co-ordinate to your correct IP range, exterior of your DHCP range.

Overclocking

Information technology is all-time to have your rig stable for 24 hours before attempting overclocks.

  1. Follow the instructions on http://ethosdistro.com/puddle.txt to set overclocks globally, or for individual rigs.
  2. Afterwards you prepare overclocks, you tin either reboot, and the rig will accept the new config and employ the new clocks automatically, or you can run putconf && ethos-overclock, and your rig volition use the overclocks during the mining session.
  3. Use testify miner to watch the miner log.

Annotation: If your rig crashes or hangs subsequently setting overclocks, follow the beneath guide:

  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

If your GPUs reach near the maxgputemp, all fans will set to 100%, and all GPUs will endeavor to become into a lower power land.

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

Follow the below steps to reduce the chances of your GPUs overheating:

  • Exercise not set fan speed on individual GPUs, set globalfan to a higher value.
  • Remove -tt from the claymore flags options, (using claymore fan command will break globalfan).
  • Bank check to make sure in that location are no broken fans or loose cables in the GPU fans.
  • Move the GPUs around in your rig, make certain that the hottest i has ample spacing for airflow.
  • Physically swap the locations of the coldest and hottest GPUs in your rig, to balance temperatures.
  • Set maxgputemp to a higher value.
  • Point a box fan at your rig, with the air flowing from the back of the GPU, out through the metal Fifty-shaped IO brackets.
  • Repaste the GPU with thermal repaste, following the gpuShack repaste guide.

To reset all temperature-related weather condition, 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 fashion, all rigs on i network can report to the same panel.

If your public IP changes, your panel ID will alter. You can run helpme to become your electric current ethOS stats panel link.

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

  • Set custompanel publicsecret in your config (EXACTLY 12 ALPHANUMERIC CHARACTERS, must be the Aforementioned code on all your rigs).
  • public (EXACTLY half dozen ALPHANUMERIC CHARACTERS!) is your preferred panel ID.
  • underground (EXACTLY 6 ALPHANUMERIC CHARACTERS!) is your private primal.
  • r to reboot.
  • Example Right usage: custompanel ethmanmg9490 will brand all your rigs study to http://ethman.ethosdistro.com
  • Case INCORRECT usage: custompanel ethman will do nothing.

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 puddle-side constructive hashrate to run across your true hashrate for the entire rig.

If, afterwards mining for 24 hours, your pool effective hashrate is unexpectedly depression, follow the beneath guide:

  1. Brand certain that you are connecting to your pool via stratum.
    Do not employ the pool config option if your node or pool is non on your local network, and make sure stratumproxy is enabled, and proxypool1 and proxypool2 are divers, as per the sample config located at http://ethosdistro.com/puddle.txt.
  2. Ping your puddle domain and make sure there is no packet loss (example: ping us1.ethermine.org)
    If there is parcel loss, use another pool server that is closer to your geographic location.
  3. Reboot your rig.
  4. If you yet get low hashrate, and if the router that your rig is connected to is also serving wifi, plough off the wifi feature and monitor the rig performance for another 24 hours.
  5. If the event is resolved after disabling wifi, set up a dedicated router for your rig(s), and disable the wifi characteristic 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 Eolith coin and select Ether (or whatever 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 (Yous tin can make an Ether Refund Address at myetherwallet.com)
  6. Checkmark I agree to terms and click Get-go Transaction.
  7. You lot volition go a permanent receiving address. This address is controlled past Shapeshift, which will autotrade all deposits to Bitcoin, and transport them to your Bitcoin Accost.
  8. Set Shapeshift'due south 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 increment, hashrate lowers slightly. This is normal.
  • Mining ethash on 3GB GPUs requires at to the lowest degree ethOS 1.iii.3 and Claymore 12 to run correctly.
  • You cannot intermix Hard disk/R7/R9 with RX and/or with NVIDIA in the same rig. They use unlike drivers that cannot work together.
  • You lot can mine EXP, ETC and other ethash/daggerhashimoto coins just by switching pools and wallets.
  • A crashed GPU becomes cold and ordinarily reduces memclock. This is visible in your ethosdistro.com stats panel.
  • The best powertune value for R9 290/x/390/x is fifty.
  • The best core clock for R9 285/380 is 800mhz, which will reduce power and temperature usage with minimal consequence on hashrate.
  • In most cases, adjusting gpu memory clock volition result in instability. The all-time value is the default manufactory retentivity clock.
  • The Asus B250 Mining Practiced is nigh stable by plugging in GPUs using the below configuration:

b250

Using TeamViewer with ethOS

  1. Update ethOS.
  2. Kicking into ethOS locally, with a monitor fastened.
  3. Run the teamviewer command in the terminal.
  4. Read and accept the EULA; when the Welcome Wagon appears, click "Close".
  5. In the TeamViewer window, click "Connection" -> "Setup Unattended Admission".
  6. In the Unattended Access wizard, click "Next".
    1. Practice not alter the computer name, and set your password (this will be your remote access password).
    2. Select "I don't want to create a TeamViewer account now", then click "Side by side".
  7. Click "Finish" to consummate the wizard, and relieve your Connectedness Id Number.
  8. Download and install "TeamViewer for Remote Control" for your PC, Tablet, or Phone, and start the awarding in that location.
  9. Enter the TeamViewer ID Number that you saved earlier, then press "Remote Control".
  10. Enter the countersign that you set earlier, and press "OK".
  • To disable TeamViewer: run rm /home/ethos/.config/teamviewer/client.conf
  • To delete TeamViewer: run remove-teamviewer (available every bit of ethOS 1.ii.9).

NOTE: If TeamViewer is deleted, reimaging ethOS is the only manner to reinstall it.

DOWNLOAD HERE

Posted by: williamsdeach1985.blogspot.com

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel