linux设置抽成命令,ethminer 新版指令參數挖 ETH 簡易教學

Usage ethminer [OPTIONS]

Options:

Work farming mode:

-F,--farm (deprecated) Put into mining farm mode with the work server at URL (default: http://127.0.0.1:8545)

-FF,-FO, --farm-failover, --stratum-failover (deprecated) Failover getwork/stratum URL (default: disabled)

--farm-retries Number of retries until switch to failover (default: 3)

-S, --stratum (deprecated) Put into stratum mode with the stratum server at host:port

-SF, --stratum-failover (deprecated) Failover stratum server at host:port

-O, --userpass (deprecated) Stratum login credentials

-FO, --failover-userpass (deprecated) Failover stratum login credentials (optional, will use normal credentials when omitted)

--work-timeout reconnect/failover after n seconds of working on the same (stratum) job. Defaults to 180. Don't set lower than max. avg. block time

--stratum-ssl [] (deprecated) Use encryption to connect to stratum server.

0: Force TLS1.2 (default)

1: Allow any TLS version

2: Allow self-signed or invalid certs and any TLS version

-SP, --stratum-protocol (deprecated) Choose which stratum protocol to use:

0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)

1: eth-proxy compatible: dwarfpool, f2pool, nanopool (required for hashrate reporting to work with nanopool)

2: EthereumStratum/1.0.0: nicehash

-RH, --report-hashrate Report current hashrate to pool (please only enable on pools supporting this)

-HWMON [], Displays gpu temp, fan percent and power usage. Note: In linux, the program uses sysfs, which may require running with root privileges.

0: Displays only temp and fan percent (default)

1: Also displays power usage

--exit Stops the miner whenever an error is encountered

-SE, --stratum-email Email address used in eth-proxy (optional)

--farm-recheck Leave n ms between checks for changed work (default: 500). When using stratum, use a high value (i.e. 2000) to get more stable hashrate output

-P URL Specify a pool URL. Can be used multiple times. The 1st for for the primary pool, and the 2nd for the failover pool.

URL takes the form: scheme://user[:password]@hostname:port[/emailaddress].

for getwork use one of the following schemes:

http

for stratum use one of the following schemes:

stratum+ssl stratum+tcp stratum+tls stratum+tls12 stratum1+ssl stratum1+tcp stratum1+tls stratum1+tls12 stratum2+ssl stratum2+tcp stratum2+tls stratum2+tls12

Example 1 : stratum+ssl://0x012345678901234567890234567890123.miner1@ethermine.org:5555

Example 2 : stratum1+tcp://0x012345678901234567890234567890123.miner1@nanopool.org:9999/john.doe@gmail.com

Example 3 : stratum1+tcp://0x012345678901234567890234567890123@nanopool.org:9999/miner1/john.doe@gmail.com

Benchmarking mode:

-M [],--benchmark [] Benchmark for mining and exit; Optionally specify block number to benchmark against specific DAG.

--benchmark-warmup Set the duration of warmup for the benchmark tests (default: 3).

--benchmark-trial Set the duration for each trial for the benchmark tests (default: 3).

--benchmark-trials Set the number of benchmark trials to run (default: 5).

Simulation mode:

-Z [],--simulation [] Mining test mode. Used to validate kernel optimizations. Optionally specify block number.

Mining configuration:

-G,--opencl When mining use the GPU via OpenCL.

-U,--cuda When mining use the GPU via CUDA.

-X,--cuda-opencl Use OpenCL + CUDA in a system with mixed AMD/Nvidia cards. May require setting --opencl-platform 1 or 2. Use --list-devices option to check which platform is your AMD.

--opencl-platform When mining using -G/--opencl use OpenCL platform n (default: 0).

--opencl-device When mining using -G/--opencl use OpenCL device n (default: 0).

--opencl-devices <0 1 ..n> Select which OpenCL devices to mine on. Default is to use all

-t, --mining-threads Limit number of CPU/GPU miners to n (default: use everything available on selected platform)

--list-devices List the detected OpenCL/CUDA devices and exit. Should be combined with -G, -U, or -X flag

--display-interval Set mining stats display interval in seconds. (default: every 5 seconds)

-L, --dag-load-mode DAG generation mode.

parallel - load DAG on all GPUs at the same time (default)

sequential - load DAG on GPUs one after another. Use this when the miner crashes during DAG generation

single - generate DAG on device n, then copy to other devices

OpenCL configuration:

--cl-kernel Use a different OpenCL kernel (default: use stable kernel)

0: stable kernel

1: experimental kernel

--cl-local-work Set the OpenCL local work size. Default is 128

--cl-global-work Set the OpenCL global work size as a multiple of the local work size. Default is 8192 * 128

--cl-parallel-hash <1 2 ..8> Define how many threads to associate per hash. Default=8

CUDA configuration:

--cuda-block-size Set the CUDA block work size. Default is 128

--cuda-grid-size Set the CUDA grid size. Default is 8192

--cuda-streams Set the number of CUDA streams. Default is 2

--cuda-schedule Set the schedule mode for CUDA threads waiting for CUDA devices to finish work. Default is 'sync'. Possible values are:

auto - Uses a heuristic based on the number of active CUDA contexts in the process C and the number of logical processors in the system P. If C > P, then yield else spin.

spin - Instruct CUDA to actively spin when waiting for results from the device.

yield - Instruct CUDA to yield its thread when waiting for results from the device.

sync - Instruct CUDA to block the CPU thread on a synchronization primitive when waiting for the results from the device.

--cuda-devices <0 1 ..n> Select which CUDA GPUs to mine on. Default is to use all

--cuda-parallel-hash <1 2 ..8> Define how many hashes to calculate in a kernel, can be scaled to achieve better performance. Default=4

--cuda-noeval bypass host software re-evaluation of GPU solutions.

This will trim some milliseconds off the time it takes to send a result to the pool.

Use at your own risk! If GPU generates errored results they WILL be forwarded to the pool

Not recommended at high overclock.

API core configuration:

--api-port Set the api port, the miner should listen to. Use 0 to disable. Default=0, use negative numbers to run in readonly mode. for example -3333.

General Options:

-v,--verbosity <0 - 9> Set the log verbosity from 0 to 9 (default: 5). Set to 9 for switch time logging.

-V,--version Show the version and exit.

-h,--help Show this help message and exit.

Environment variables:

NO_COLOR - set to any value to disable color output. Unset to re-enable color output.

  • 0
    点赞
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
# ethminer [![standard-readme compliant](https://img.shields.io/badge/readme style-standard-brightgreen.svg)](https://github.com/RichardLitt/standard-readme) [![Gitter](https://img.shields.io/gitter/room/nwjs/nw.js.svg)][Gitter] [![Releases](https://img.shields.io/github/downloads/ethereum-mining/ethminer/total.svg)][Releases] > Ethereum miner with OpenCL, CUDA and stratum support **Ethminer** is an Ethash GPU mining worker: with ethminer you can mine every coin which relies on an Ethash Proof of Work thus including Ethereum, Ethereum Classic, Metaverse, Musicoin, Ellaism, Pirl, Expanse and others. This is the actively maintained version of ethminer. It originates from [cpp-ethereum] project (where GPU mining has been discontinued) and builds on the improvements made in [Genoil's fork]. See [FAQ](#faq) for more details. ### Features - OpenCL mining - Nvidia CUDA mining - realistic benchmarking against arbitrary epoch/DAG/blocknumber - on-GPU DAG generation (no more DAG files on disk) - stratum mining without proxy - OpenCL devices picking - farm failover (getwork + stratum) ## Table of Contents - [Install](#install) - [Usage](#usage) - [Examples connecting some pools](#examples-connecting-some-pools) - [Build](#build) - [Continuous Integration and development builds](#continuous-integration-and-development-builds) - [Building from source](#building-from-source) - [CMake configuration options](#cmake-configuration-options) - [Maintainer](#maintainer) - [Contribute](#contribute) - [F.A.Q.](#faq) ## Install [![Releases](https://img.shields.io/github/downloads/ethereum-mining/ethminer/total.svg)][Releases] Standalone **executables** for _Linux_, _macOS_ and _Windows_ are provided in the [Releases] section. Download an archive for your operating system and unpack the content to a place accessible from command line. The ethminer is ready to go. | Builds | Release | Date | | ------ | ------- | ---- | | Last | [![GitHub release](https://img.shields.io/github/release/ethereum-mining/ethminer/all.svg)](https://github.com/ethereum-mining/ethminer/releases) | [![GitHub Release Date](https://img.shields.io/github/release-date-pre/ethereum-mining/ethminer.svg)](https://github.com/ethereum-mining/ethminer/releases) | | Stable | [![GitHub release](https://img.shields.io/github/release/ethereum-mining/ethminer.svg)](https://github.com/ethereum-mining/ethminer/releases) | [![GitHub Release Date](https://img.shields.io/github/release-date/ethereum-mining/ethminer.svg)](https://github.com/ethereum-mining/ethminer/releases) | ## Usage The **ethminer** is a command line program. This means you launch it either from a Windows command prompt or Linux console, or create shortcuts to predefined command lines using a Linux Bash script or Windows batch/cmd file. For a full list of available command, please run: ```sh ethminer --help ``` ### Examples connecting some pools Check our [samples](POOL_EXAMPLES_ETH.md) to see how to connect to different pools. ## Build ### Continuous Integration and development builds | CI | OS | Status | Development builds | | ------------- | ------------- | ----- | ----------------- | | [Travis CI] | Linux, macOS | [![Travis CI](https://img.shields.io/travis/ethereum-mining/ethminer.svg)][Travis CI] | ✗ No build artifacts, [Amazon S3 is needed] for this | | [AppVeyor] | Windows | [![AppVeyor](https://img.shields.io/appveyor/ci/ethereum-mining/ethminer.svg)][AppVeyor] | ✓ Build artifacts available for all PRs and branches | The AppVeyor system automatically builds a Windows .exe for every commit. The latest version is always available [on the landing page](https://ci.appveyor.com/project/ethereum-mining/ethminer) or you can [browse the history](https://ci.appveyor.com/project/ethereum-mining/ethminer/history) to access previous builds. To download the .exe on a build under 'JOB NAME' select 'Configuration: Release', choose 'ARTIFACTS' then download the zip file. ### Building from source This project uses [CMake] and [Hunter] package manager. 1. Make sure git submodules are up to date ```sh git submodule update --init --recursive ``` 2. Create a build directory. ```sh mkdir build; cd build ``` 3. Configure the project with CMake. Check out additional [configuration options](#cmake-configuration-options). ```sh cmake .. ``` Note: In Windows, it is possible to have issues with VS 2017 compilers, in that case, use VS 2017 installer to get VS 2015 compilers and use: ```sh cmake .. -G "Visual Studio 15 2017 Win64" -Tv140,host=x64 ``` 4. Build the project using [CMake Build Tool Mode]. This is a portable variant of `make`. ```sh cmake --build . ``` Note: In Windows, it is possible to have compiler issues if you don't specify build config. In that case use: ```sh cmake --build . --config Release ``` 5. _(Optional, Linux only)_ Install the built executable. ```sh sudo make install ``` #### OpenCL support on Linux If you're planning to use [OpenCL on Linux](https://github.com/ruslo/hunter/wiki/pkg.opencl#pitfalls) you have to install OpenGL libraries. E.g. on Ubuntu run: ```sh sudo apt-get install mesa-common-dev ``` #### Disable Hunter If you want to install dependencies yourself or use system package manager you can disable Hunter by adding [-DHUNTER_ENABLED=OFF](https://docs.hunter.sh/en/latest/reference/user-variables.html#hunter-enabled) to configuration options. ### CMake configuration options Pass these options to CMake configuration command, e.g. ```sh cmake .. -DETHASHCUDA=ON -DETHASHCL=OFF ``` - `-DETHASHCL=ON` - enable OpenCL mining, `ON` by default, - `-DETHASHCUDA=ON` - enable CUDA mining, `ON` by default. - `-DAPICORE=ON` - enable API Server, `ON` by default. - `-DETHDBUS=ON` - enable D-Bus support, `OFF` by default. ## Maintainer [![Gitter](https://img.shields.io/gitter/room/ethereum-mining/ethminer.svg)][Gitter] - Paweł Bylica [@chfast](https://github.com/chfast) ## Contribute [![Gitter](https://img.shields.io/gitter/room/ethereum-mining/ethminer.svg)][Gitter] To meet the community, ask general questions and chat about ethminer join [the ethminer channel on Gitter][Gitter]. All bug reports, pull requests and code reviews are very much welcome. ## License Licensed under the [GNU General Public License, Version 3](LICENSE). ## F.A.Q 1. Why is my hashrate with Nvidia cards on Windows 10 so low? The new WDDM 2.x driver on Windows 10 uses a different way of addressing the GPU. This is good for a lot of things, but not for ETH mining. For Kepler GPUs: I actually don't know. Please let me know what works best for good old Kepler. For Maxwell 1 GPUs: Unfortunately the issue is a bit more serious on the GTX750Ti, already causing suboptimal performance on Win7 and Linux. Apparently about 4MH/s can still be reached on Linux, which, depending on ETH price, could still be profitable, considering the relatively low power draw. For Maxwell 2 GPUs: There is a way of mining ETH at Win7/8/Linux speeds on Win10, by downgrading the GPU driver to a Win7 one (350.12 recommended) and using a build that was created using CUDA 6.5. For Pascal GPUs: You have to use the latest WDDM 2.1 compatible drivers in combination with Windows 10 Anniversary edition in order to get the full potential of your Pascal GPU. 2. Why is a GTX 1080 slower than a GTX 1070? Because of the GDDR5X memory, which can't be fully utilized for ETH mining (yet). 3. Are AMD cards also affected by slowdowns with increasing DAG size? Only GCN 1.0 GPUs (78x0, 79x0, 270, 280), but in a different way. You'll see that on each new epoch (30K blocks), the hashrate will go down a little bit. 4. Can I still mine ETH with my 2GB GPU? Not really, your VRAM must be above the DAG size (Currently about 2.15 GB.) to get best performance. Without it severe hash loss will occur. 5. What are the optimal launch parameters? The default parameters are fine in most scenario's (CUDA). For OpenCL it varies a bit more. Just play around with the numbers and use powers of 2. GPU's like powers of 2. 6. What does the `--cuda-parallel-hash` flag do? [@davilizh](https://github.com/davilizh) made improvements to the CUDA kernel hashing process and added this flag to allow changing the number of tasks it runs in parallel. These improvements were optimised for GTX 1060 GPUs which saw a large increase in hashrate, GTX 1070 and GTX 1080/Ti GPUs saw some, but less, improvement. The default value is 4 (which does not need to be set with the flag) and in most cases this will provide the best performance. 7. What is ethminer's relationship with [Genoil's fork]? [Genoil's fork] was the original source of this version, but as Genoil is no longer consistently maintaining that fork it became almost impossible for developers to get new code merged there. In the interests of progressing development without waiting for reviews this fork should be considered the active one and Genoil's as legacy code. 8. Can I CPU Mine? No, use geth, the go program made for ethereum by ethereum. 9. CUDA GPU order changes sometimes. What can I do? There is an environment var `CUDA_DEVICE_ORDER` which tells the Nvidia CUDA driver how to enumerates the graphic cards. Following values are valid: * FASTEST_FIRST (Default) - causes CUDA to guess which device is fastest using a simple heuristic. * PCI_BUS_ID - orders devices by PCI bus ID in ascending order. To prevent some unwanted changes in the order of your CUDA devices you **might set the environment to `PCI_BUS_ID`**. This can be done: * Linux: * Adapt /etc/environment file and add a line `CUDA_DEVICE_ORDER=PCI_BUS_ID` * Adapt your start script launching ethminer and add a line `export CUDA_DEVICE_ORDER=PCI_BUS_ID` * Windows: * Adapt your environment using the control panel (just search `setting environment windows control panel` using your favorite search engine) * Adapt your start (.bat) file launching ethminer and add a line `setx CUDA_DEVICE_ORDER=PCI_BUS_ID` or `set CUDA_DEVICE_ORDER=PCI_BUS_ID` * For more details about `setx` and `set` see [Amazon S3 is needed]: https://docs.travis-ci.com/user/uploading-artifacts/ [AppVeyor]: https://ci.appveyor.com/project/ethereum-mining/ethminer [CMake]: https://cmake.org/ [CMake Build Tool Mode]: https://cmake.org/cmake/help/latest/manual/cmake.1.html#build-tool-mode [cpp-ethereum]: https://github.com/ethereum/cpp-ethereum [Genoil's fork]: https://github.com/Genoil/cpp-ethereum [Gitter]: https://gitter.im/ethereum-mining/ethminer [Hunter]: https://docs.hunter.sh/ [Releases]: https://github.com/ethereum-mining/ethminer/releases [Travis CI]: https://travis-ci.org/ethereum-mining/ethminer

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值