PhoenixMiner — 전체 사용 설명서
PhoenixMiner는 Claymore의 듀얼 Ethereum 마이너 명령줄 옵션 대부분을 지원하므로
Claymore 마이너에서 쓰던 명령줄 옵션을 그대로 사용할 수 있습니다.
풀 옵션:
-pool <host:port> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal <wallet> Ethash wallet (some pools require appending of user name and/or worker)
-pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure)
-worker <name> Ethash worker name (most pools accept it as part of wallet)
-proto <n> Selects the kind of stratum protocol for the ethash pool:
1: miner-proxy stratum spec (e.g. coinotron)
2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
3: qtminer (e.g. ethpool)
4: EthereumStratum/1.0.0 (e.g. nicehash)
5: EthereumStratum/2.0.0
-coin <coin> Ethash coin to use for devfee to avoid switching DAGs:
auto: Try to determine from the pool address (default)
eth: Ethereum
etc: Ethereum Classic
exp: Expanse
music: Musicoin
ubq: UBIQ
pirl: Pirl
ella: Ellaism
etp: Metaverse ETP
whale: WhaleCoin
vic: Victorium
nuko: Nekonium
mix: Mix
egem: EtherGem
etz: EtherZero
clo: Callisto
dbix: DubaiCoin
moac: MOAC
etho: Ether-1
yoc: Yocoin
b2g: Bitcoiin2Gen
esn: Ethersocial
ath: Atheios
reosc: REOSC
qkc: QuarkChain
bci: Bitcoin Interest
-stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no
-weakssl Skip the strict SSL certificate validation for the main ethash pool (the one specified with the -pool option)
-pool2 <host:port> Failover ethash pool address. Same as -pool but for the failover pool
-wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too)
-pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too)
-worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too)
-proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
-coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
-stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no
-weakssl2 Skip the strict SSL certificate validation for the failover ethash pool (the one specified with the -pool2 option)
-dpool <host:port> Dual mining pool address
-dwal <wallet> Dual mining wallet
-dpass <password> Dual mining pool password (most pools don't require it, use 'x' as password if unsure)
-dworker <name> Dual mining worker name
-dcoin blake2s Currently only the Blake2s algorithm is supported for dual mining. If you want to put
all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt
to force the miner to load the dual mining pools from dpools.txt
-dstales <n> Submit stales to the dual mining pool: 1 - yes (default), 0 - no
일반 풀 옵션:
-fret <n> Switch to next pool afer N failed connection attempts (default: 3)
-ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600)
-ptimeout <n> Switch back to primary pool after n minutes. This setting is 30 minutes by default;
set to 0 to disable automatic switch back to primary pool.
-retrydelay <n> Seconds to wait before reconnecting (default: 20)
-gwtime <n> Recheck period for Solo/GetWork mining (default: 200 ms)
-rate <n> Report hashrate to the pool: 1 - yes, 0 - no (1 is the default), 2 - (for solo mining only)
use alternative name of the report method "eth_submitHashRate" instead of "eth_submitHashrate"
-nosni Do not send SNI host name on SSL connections
벤치마크 모드:
-bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
If you specify only the -bench option, you will benchmark the ethash algorithm. If you want to bench
the dual mining, use the options -bench <n> -dcoin blake2s. If you want to benchmark the ProgPOW BCI
algorithm, use the options -bench <n> -coin bci
원격 제어 옵션:
-cdm <n> Selects the level of support of the CDM remote monitoring:
0: disabled
1: read-only - this is the default
2: full (only use on secure connections)
-cdmport <port> Set the CDM remote monitoring port (default is 3333). You can also specify
<ip_addr:port> if you have a secure VPN connection and want to bind the CDM port to it
-cdmpass <pass> Set the CDM remote monitoring password
-cdmrs Reload the settings if config.txt is edited/uploaded remotely. Note that most options require restart in order to change.
Currently the follwing options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, -gpow, and most of the
hardware control parameters (-tt, -fcm, -fanmin, -fanmax, -powlim, -tmax, -ttli, -cclock, -cvddc, -mclock,
-mvddc, -ppf, -straps, -vmt1, -vmt2, -vmt3, -vmr)
채굴 옵션:
-amd Use only AMD cards
-acm Turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console.
-nvidia Use only Nvidia cards
-nvmalt Use alternative NVML initialization. Use this option if the program crashes or exits while showing Initializing NVML... on the console.
-gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma)
-mi <n> Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU.
-gt <n> Set the GPU tuning parameter (6 to 400). The default is 15. You can change the
tuning parameter interactively with the '+' and '-' keys in the miner's console window.
If you don't specify -gt or you specify value 0, the miner will start auto-tuning to determine the best GT value for each GPU
Note that when the GPU is dual-mining, it ignores the -gt values, and uses -sci instead.
-sci <n> Set the dual mining intensity (1 to 1000). The default is 30. As you increase the value of -sci,
the secondary coin hashrate will increase but the price will be higher power consumption and/or
lower ethash hashrate.
You can change the this parameter interactively with the '+' and '-' keys in the miner
console window. You may specify this option per-GPU. If you set -sci to 0,
the miner will use auto-tuning to determine the best value, while trying to maximize the
ethash hashrate regardless of the secondary coin hashrate.
-clkernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative, 3 - turbo (1 is the default)
-clgreen <n> Use the power-efficient ("green") kernels (0: no, 1: yes; default: 0).
You may specify this option per-GPU. Note that you have to run auto-tune again as the
optimal GT values are completely different for the green kernels
-clnew <n> Use the new AMD kernels (0: no, 1: yes; default: 1)
-clabi <n> Use OpenCL 1.x even if 2.x is supported by the driver (0: no, 1: yes; default: 0)
-clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1)
-nvkernel <n> Type of Nvidia kernel: 0 auto (default), 1 old (v1), 2 newer (v2), 3 latest (v3).
Note that v3 kernels are only supported on GTX10x0 GPUs. Also note that dual mining is
supported only by v2 kernels. You may specify this option per-GPU.
-nvdo <n> Enable Nvidia driver-specific optimizations (0 - no, the default; 1 - yes). Try -nvdo 1 if your
are unstable. You may specify this option per-GPU.
-nvnew <n> Use new Nvidia kernels if supported (0: no, 1: yes; default: 1)
-nvf <n> Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU.
-lhr <n> Nvidia LHR unlock (0: no, -1: automatic, 100-1000: unlock intensity; default: -1).
If this option is not specified (or specified as -1), the default LHR unlock intensity is 520. You may specify this option per-GPU.
-mode <n> Mining mode (0: dual mining if dual pool(s) are specified; 1: ethash only even if dual pools are specified).
You may specify this option per-GPU.
-list List the detected GPUs devices and exit
-gbase <n> Set the index of the first GPU (0 or 1, default: 1)
-minRigSpeed <n> Restart the miner if avg 5 min speed is below <n> MH/s
-eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to
avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
-daglim <n>
(AMD Polaris, Baffin, Tonga, or Fiji cards only) Limit the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 373
on Windows (or 381 on Linux). The possible values except the exact DAG limit are also 0 (turn off the DAG limit), 1 (automatic DAG
limit size, usually 4023 MB under Windows; this is the default). Note that the hashrate will drop significantly with each epoch
after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value,
for example "-daglim 3996" or even lower.
-dagrestart <n> Restart the miner when allocating buffer for a new DAG epoch. The
possible values are: 0 - never, 1 - always, 2 - auto (the miner decides depending on the driver version).
This is relevant for 4 GB AMD cards, which may have problems with new DAG epochs after epoch 350.
-lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
(0-3, default: 0 - fastest, 3 - slowest).
-gser <n> Serializing DAG creation on multiple GPUs (0 - no serializing, all GPUs generate the DAG simultaneously, this is the default;
1 - partial overlap of DAG generation on each GPU; 2 - no overalp (each GPU waits until the previous one has finished generating the DAG);
3-10 - from 1 to 8 seconds delay after each GPU DAG generation before the next one)
-gpureset <n> Fully reset GPU when paused (0 - no, 1 - yes; default: no, except on 1080Ti). You may specify this option per-GPU.
-altinit Use alternative way to initialize AMD cards to prevent startup crashes
-rvram <n> Minimum free VRAM in MB (-1: don't check; default: 384 for Windows, and 128 for Linux)
-wdog <n> Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks
periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode
command-line parameter for the restart modes)
-wdtimeout <n> Watchdog timeout (30 - 300; default 45 seconds). You can use this parameter to increase
the default watchdog timeout in case it restarts the miner needlessly
-rmode <n> Selects the restart mode when a GPU crashes or freezes:
0: disabled - miner will shut down instead of restarting
1: restart with the same command line options - this is the default
2: reboot (shut down miner and execute reboot.bat)
-log <n> Selects the log file mode:
0: disabled - no log file will be written
1: write log file but don't show debug messages on screen (default)
2: write log file and show debug messages on screen
-logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be
replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there
is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you
want to use the same logfile but the contents to be overwritten every time when you start the miner,
put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$).
-logdir <path> Set a path where the logfile(s) will be created
-logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation).
On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a
single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one
is created.
-config <name> Load a file with configuration options that will be added to the command-line options.
Note that the order is important. For example, if we have a config.txt file that contains -cclock 1000
and we specify command line -cclock 1100 -config config.txt, the options from the config.txt file will take
precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100)
then the second option takes precedence and the resulting -cclock will be 1100. Note that only one -config
option is allowed. Also note that if you reload the config file with 'c' key or with the remote interface,
its options will take precedence over whatever you have specified in the command-line.
-timeout <n> Restart miner according to -rmode after n minutes
-pauseat <hh:mm> Pause the miner at hh::mm (24 hours time). You can specify multiple times: -pauseat 6:00,12:00
-resumeat <hh:mm> Resume the miner at hh::mm (24 hours time). You can specify multiple times: -resumeat 8:00,22:00
-gswin <n> GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats)
-gsi <n> Speed stats interval (5-30 sec; default: 5; use 0 to disable). The detailed stats are still
shown every 45 seconds and aren't affected by the -gsi value
-astats <n> Show advanced stats from Web sources (0: no; 1: yes). By default the coin exchange rates are updated every
4 hours, and the coin difficulty is updated every 8 hours. You can increase these periods by specifying
for example -astats 12, which will increase update periods to 12 and 24 hours respectively
-gpow <n> Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead
-li <n> Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0.
-resetoc Reset the hardware overclocking settings on startup
-leaveoc Do not reset overclocking settings when closing the miner
하드웨어 제어 옵션 (GPU마다 다른 값을 지정하려면 쉼표를 사용하세요):
-tt <n> Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %)
-ttj <n> Set fan control target hotspot (junction) temperature (can be used
only on GPUs that report the junction temperature). Example: -ttj 75 will keep the junction temperature at or bellow 75C by
increasing the fan speed as necessary. This parameter can be combined with -tt, and -ttmem
-ttmem <n> Set fan control target video memory temperature (can be used only
on GPUs that report the VRAM temperature). Example: -ttmem 83 will keep the GPU memory temperature at or
bellow 83C by increasing the fan speed as necessary. This parameter can be combined with -tt, and -ttj
-hstats <n> Level of hardware monitoring: 0 - temperature and fan speed only; 1 - temperature, fan speed, and power;
2 - full (include core/memory clocks, voltages, P-states). The default is 1.
-pidle <n> Idle power consumption of the rig in W. Will be added to the GPU power consumption when
calculating the total power consumption of the rig.
-ppf <n> The power usage of each GPU will be multiplied by this value to get the actual usage. This value is
in percent, so for example if the GPU reports 100 W power usage and you have specified -ppf 106 the GPU
power usage will be calculated to be 100 * (106 / 100) = 106 W. This allows you to correct for the efficiency
of the PSUs and the individual GPUs. You can also specify this value for each GPU separately.
-prate <n> Price of the electricity in USD per kWh (e.g. -prate 0.1). If specified the miner will calculate the
rig daily electricity cost
-fanmin <n> Set fan control min speed in % (-1 for default)
-fanmax <n> Set fan control max speed in % (-1 for default)
-fanstop <n> (AMD cards under Windows only) If set to 0 (the default), and a
fixed fan speed (e.g. -tt -40), or -fanmin is used, the miner will not allow the fans to stop rotating.
If set to 1, PhoenixMiner will not interfere in the fan stop function of the card.
-fcm <n> Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 - forced fan control; default: 0)
-tmax <n> Set fan control max temperature (0 for default)
-powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default)
-cclock <n> Set GPU core clock in MHz (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-cvddc <n> Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-mclock <n> Set GPU memory clock in MHz (0 for default)
-mvddc <n> Set GPU memory voltage in mV (0 for default)
-tstop <n> Pause a GPU when temp is >= n deg C (0 for default; i.e. off)
-tstart <n> Resume a GPU when temp is <= n deg C (0 for default; i.e. off)
-mt <n> VRAM timings (AMD under Windows only): 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings.
The default is 0. This is useful for mining with AMD cards without modding the VBIOS. If you have modded BIOS,
it is probably faster than even -mt 2
-leavemt Do not reset memory timing level ("-mt") to 0 when closing
-ttli <n> Lower GPU usage when GPU temperature is above n deg C. The default value is 0, which means do not lower the usage regardless of the
GPU temperature. This option is useful whenever -tmax is not working. If you are using both -tt and -ttli options, the
temperature in -tt should be lower than the -ttli to avoid throttling the GPUs without using the fans to properly cool them first.
-tmaxj <n> Lower GPU usage when hotspot (junction) temperature is above n deg C (can be used only on GPUs that report the junction temperature).
The default value is 0, which means do not lower the usage regardless of the GPU hotspot temperature. If you are using both
-ttj and -tmaxj options, the temperature in -ttj should be lower than the -tmaxj to avoid throttling the GPUs without using
the fans to properly cool them first.
-tmaxmem <n> Lower GPU usage when VRAM temperature is above n deg C (can be used only on GPUs that report the memory temperature).
The default value is 0, which means do not lower the usage regardless of the GPU memory temperature. If you are using both
-ttmem and -tmaxmem options, the temperature in -ttmem should be lower than the -tmaxmem to avoid throttling the GPUs
without using the fans to properly cool them first.
-straps <n> Memory strap level (Nvidia cards 10x0 and P10x series only). The possible values are 0 to 6. 0 is the default value and uses the default
timings from the VBIOS. Each strap level corresponds to a predefined combination of memory timings (-vmt1, -vmt2,
-vmt3, -vmr). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than
the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
-straps <n> Memory strap level (AMD Vega cards only). The possible values are 0 to 5. 0 is the default value and uses the default timings from the
VBIOS. Each strap level corresponds to a predefined combination of memory timings. Strap level 5 is the fastest level and may not work
on most cards, 1 is the slowest (but still faster than the default timings). Note that straps for AMD cards are experimental and may
lead to crashes or instability. "-vmt1", "-vmt2", and "-vmt3" parameters have no effect on AMD cards
-vmt1 <n> Memory timing parameter 1 (0 to 100, default 0)
-vmt2 <n> Memory timing parameter 2 (0 to 100, default 0)
-vmt3 <n> Memory timing parameter 3 (0 to 100, default 0)
-vmr <n> Memory refresh rate (0 to 100, default 0). For AMD cards you may also use "-rxboost"
-nvmem <n> Force using straps on unsupported Nvidia GPUs (0 - do not force, 1 - GDDR5, 2 - GDDR5X). Make sure that the parameter matches your GPU
memory type. You can try this if your card is Pascal-based but when you try to use -straps or any other memory timing option, the card
is shown as "unsupported".
-rxboost <n> Memory refresh rate on AMD cards (0 - default values, 1 - predefined value that should work on most cards, 2 to 100 -
increasingly aggressive settings). If you want to fine tune the value, you may run the miner with "-rxboost 1", write down the
corresponding "-vmr" values that are showed in the log file, and then use "-vmr" instead with adjusted values.
-vmdag <n> Reset straps to default during DAG generation (default: 1)
-mcdag <n> Reset GPU memory clock to default during DAG generation. Nvidia
only, default: 0 (turned off). This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG
buffer, which can lead to excessive number of stale shares.
Under Linux this option will execute the daggen.sh script (if present in the current directory) for each GPU, passing the GPU
index as the first argument, and PCIE bus ID as second argument. The miner will not wait for the daggen.sh script to finish before
starting to generate the DAGs. Instead it will for a fixed 7 seconds. This allows you to do all the following in the
daggen.sh: turn off the overclocking of Nvidia GPUs, sleep for 30-60 seconds, and then re-apply the overclocking of the Nvidia GPUs.
일반 옵션:
-v,--version Show the version and exit -vs Show short version string (e.g. "4.1c") and exit -h,--help Show information about the command-line options and exit
GPU별 옵션
PhoenixMiner의 일부 옵션은 모든 GPU에 같은 값을 적용할 수도 있고,
GPU마다 다른 값을 적용할 수도 있습니다. 예를 들어, 모든 그래픽카드에 -gt 값을 지정하려면
-gt 90이라고 쓰면 되지만, 그래픽카드마다 다른 GT 값을 지정하려면 다음과 같이 씁니다:
GPU 5장짜리 채굴 장비라면 -gt 20,15,40,90,90. 이렇게 하면 첫 번째 GPU의 GT는 20, 두 번째
GPU는 15, 이런 식으로 설정됩니다. GPU 개수보다 적은 값을 지정하면 나머지 GPU는 해당 매개변수의
기본값을 사용합니다.
그래픽카드마다 다른 값을 지정하는 더 유연한 방법도 있습니다.
예시로 설명하는 것이 가장 좋습니다: -cclock *:1100,1-3:1090,4:1300 - 여기서는 코어 클럭을
모든 그래픽카드에 1100 MHz로 설정하되, 1~3번 그래픽카드는 1090 MHz, 4번 그래픽카드는 1300 MHz로 설정합니다.
콜론(:) 앞부분은 선택자로, 콜론 뒤의 값이 적용될 GPU를 선택합니다. 선택자는 다음과 같을 수 있습니다:
- single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU
- range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5
- asterisk, which sets the value for all GPUs
- label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards
- arbitrary string that starts with letter and can contain letters, numbers and asterisks,
which is matched with the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will
set value +500 for all cards which contain 'gtx' and '1070' in their names with anything
between them. This will match 'Nvidia GeForce GTX 1070' but not 'Nvidia GeForce 1070'.
하나의 그래픽카드에 여러 선택자가 일치하면 마지막 선택자만 적용됩니다.
예: -cclock *:1100,1-4:1090,2:1300은 2번 그래픽카드를 1300으로, 1, 3, 4번 그래픽카드를 1090으로,
나머지 그래픽카드를 코어 클럭 1100 MHz로 설정합니다.
또한 마이너가 실행 중일 때 다음 대화형 명령을 사용할 수 있습니다.
콘솔 창에서 다음 키 중 하나를 누르세요:
s Print detailed statistics 1-9 Pause/resume GPU1 ... GPU9 (if you have more than 9 GPUs, type 010 for card 10, 011 for card 11, etc.) p Pause/resume the whole miner +,- Increase/decrease GPU tuning parameter g Reset the GPU tuning parameter (and stop auto-tuning if active) x Select the GPU(s) for manual or automatic GT tuning z Start AMD auto-tune process r Reload epools.txt and switch to primary ethash pool e Select the current ethash pool (if you have more than 9 pools in the list, type 010 for pool 10, 011 for pool 11, etc.) d Select the current dual-mining pool y Turn on AMD Compute mode if it is off on some of the GPUs c Reload the config.txt file (some settings require restart, see -cdmrs option above for details) h Print this short help
설정 파일
PhoenixMiner는 Claymore의 듀얼 Ethereum 마이너와 같은 설정 파일을 지원하므로
기존 설정 파일을 변경 없이 그대로 사용할 수 있습니다.
명령줄 옵션 대신 설정 파일로 PhoenixMiner를 제어할 수도 있습니다.
PhoenixMiner.exe를 옵션 없이 실행하면 현재 디렉터리에서 config.txt 파일을 찾아
그 파일에서 명령줄 옵션을 읽습니다. 원한다면 PhoenixMiner.exe를 실행할 때
유일한 명령줄 옵션으로 파일 이름을 지정하여
다른 이름의 파일을 사용할 수도 있습니다.
PhoenixMiner 디렉터리에 config.txt 예제 파일이 있습니다.
명령줄에 풀을 직접 지정하는 대신 epools.txt라는 별도의 설정 파일을
사용할 수도 있습니다. 이 파일에는 한 줄에 하나씩 풀을 지정합니다 (PhoenixMiner 디렉터리에
epools.txt 예제 파일이 있습니다).
듀얼 채굴 풀에는 epools.txt와 같은 형식이지만 보조 코인용인
dpools.txt 파일을 사용할 수 있습니다. PhoenixMiner 디렉터리에 epools.txt 예제 파일이 있습니다.
마이너가 시작될 때마다 로드되는 epools.txt와 달리, dpools.txt 파일은
명령줄에서 -dpool로 듀얼 채굴 풀을 지정하거나 최소한
-dcoin blake2s 명령줄 옵션을 추가한 경우에만 읽힙니다.
config.txt와 epools.txt/dpools.txt 파일을 사용하면 다음과 같은 장점이 있습니다:
- 채굴 장비가 여러 대라면 이 파일들로 모든 설정을 복사해 붙여넣을 수 있습니다
- 원격으로 채굴 장비를 제어한다면 새 epools.txt 파일을 마이너에 업로드하거나,
새 config.txt 파일을 업로드하고 마이너를 재시작하여 풀은 물론 마이너 옵션까지
변경할 수 있습니다.
원격 모니터링 및 관리
Phoenix miner는 원격 모니터링 및 관리를 위한 Claymore 듀얼 마이너 프로토콜과 완전히
호환됩니다. 즉, Claymore 듀얼 마이너를 지원하도록 만들어진 모든 도구를 사용할 수 있으며,
Claymore 듀얼 마이너 패키지에 포함된 "Remote manager" 애플리케이션도 사용할 수 있습니다.
저희는 훨씬 더 강력하고 안전한 원격 모니터링 및 제어 기능과
컨트롤 센터 애플리케이션을 개발 중이며, 이를 통해 원격 또는 로컬 채굴 장비를 더 잘 제어하고
채굴 수익을 높일 수 있는 독자적인 기능을 제공할 예정입니다.
하드웨어 제어 옵션
하드웨어 제어 옵션에 관한 몇 가지 중요한 참고 사항:
최신 Nvidia 드라이버는 하드웨어 제어를 허용하려면 관리자 권한(Linux에서는 root)으로 실행해야 하므로, VRAM 타이밍 옵션이 작동하려면 PhoenixMiner를 관리자 권한으로 실행해야 합니다.
PhoenixMiner as administrator for the VRAM timing options to work.
VRAM 타이밍 옵션("-straps", "-vmt1", "-vmt2", "-vmt3", "-vmr")을 사용할 때는 낮은 값부터 시작하고, 더 높고 공격적인 설정을 시도하기 전에 그래픽카드가 안정적인지 확인하세요. "-straps"는 다른 옵션과 함께 사용할 수 있습니다. 예를 들어 "-straps 1" "-vmt1 60"은 1단계 strap의 타이밍을 사용하되 -vmt1은 1단계 strap에 지정된 값 대신 60으로 설정합니다. 이 경우 "-straps" 옵션을 먼저 지정해야 합니다.
cards are stable before trying higher and more aggressive settings. You can use "-straps" along with the other options. For example "-straps 1" "-vmt1 60" will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the "-straps" option must be specified first.
일반적으로 "-vmt3" 옵션은 해시레이트에 거의 영향을 주지 않으므로, 먼저 다른 매개변수를 조정해 보세요.
VRAM 타이밍 옵션은 같은 모델의 GPU라도 GPU마다 상당히 다를 수 있습니다. 따라서 VRAM 타이밍 옵션은 GPU별로 지정할 수 있으며, 그렇게 하는 것이 좋습니다.
probably should) specify the VRAM timing options per-GPU.
하드웨어 제어 옵션은 Windows에서 AMD와 Nvidia 그래픽카드 모두 지원됩니다. Linux에서는 대부분의 옵션이 AMD 그래픽카드에서만 지원됩니다.
값을 하나만 지정하면(예: -cvddc 1150) 모든 그래픽카드에 적용됩니다. 그래픽카드마다 다른 값을 지정하려면 다음과 같이 쉼표로 구분합니다: -cvddc 1100,1100,1150,1120,1090 지정한 값이 GPU 개수보다 적으면 나머지 GPU는 기본값을 사용합니다.
저희는 비교적 최신 AMD GPU(RX460/470/480/560/570/580, Vega, Radeon VII, RX5700)에서만 테스트했습니다. 구형 GPU에서는 결과가 다를 수 있습니다.
AMD의 blockchain 베타 드라이버는 결과가 상당히 불안정합니다 - 전압이 아예 적용되지 않거나 얼마 후 기본값으로 되돌아가는 경우가 많습니다. 최상의 결과를 위해 대부분의 버그가 수정된 AMD의 최신 드라이버(18.5.1 이상)를 사용하세요.
-tmax는 GPU가 스로틀링을 시작해야 하는 온도를 지정합니다 (팬이 더 이상 감당하지 못하기 때문입니다).
하드웨어 제어에 다른 프로그램을 사용하면 충돌이 발생할 수 있으며, 그럴 가능성이 꽤 높습니다. 전압 등을 모니터링하려면 GPU-Z 같은 프로그램을 사용하세요. MSI Afterburner도 문제없이 동작하는 것으로 보입니다 (따라서 AMD 그래픽카드는 PhoenixMiner로 제어하고 Nvidia 그래픽카드는 MSI Afterburner로 제어할 수 있습니다).
당연한 이야기지만: 특정 클럭/전압이 서드파티 프로그램으로 설정했을 때 크래시/멈춤/잘못된 셰어를 일으킨다면, PhoenixMiner 하드웨어 제어 옵션으로 설정해도 똑같이 불안정합니다.
PhoenixMiner의 하드웨어 제어 옵션에 문제가 있고, 그동안 클럭, 팬, 전압 제어에 다른 프로그램(MSI Aftrerburner, OverdriveNTool 등)을 만족스럽게 사용해 왔다면, 그 프로그램을 계속 사용하고 PhoenixMiner의 하드웨어 제어 옵션은 무시하는 것이 가장 좋습니다 (또는 일부만 사용하고 나머지는 서드파티 도구로 계속 조정하세요).
FAQ
Q001: 왜 또 다른 마이너인가요?
A: We feel that the competition is good for the end user. In the first releases of PhoenixMiner we focused on the basic features and on the mining speed but we are now working on making our miner easier to use and even faster.
Q002: 한 채굴 장비에서 PhoenixMiner를 여러 개 실행할 수 있나요?
A: Yes, but make sure that each GPU is used by a single miner (use the -gpus, -amd, or -nvidia
command-line options to limit the GPUs that given instance of PhoenixMiner actually uses).
Another possible problem is that all instances will use the default CDM remote port 3333,
which will prevent proper remote control for all but the first instance. To fix this problem,
use the -cdmport command-line option to change the CDM remote port form its default value.
Q003: 한 채굴 장비에서 PhoenixMiner를 다른 마이너와 동시에 실행할 수 있나요?
A: Yes, but see the answer to the previous question for how to avoid problems.
Q004: 스테일 셰어란 무엇인가요?
A: The ethash coins usually have very small average block time (15 seconds in most instances). On the other hand, to achieve high mining speed we must keep the GPUs busy so we can't switch the current job too often. If our rigs finds a share just after the someone else has found a solution for the current block, our share is a stale share. Ideally, the stale shares should be minimal as same pools do not give any reward for stale shares, and even these that do reward stale shares, give only partial reward for these shares. If the share is submitted too long after the block has ended, the pool may even fully reject it.
Q005: PhoenixMiner가 보고하는 스테일 셰어 비율이 풀에 표시되는 비율보다
낮은 이유는 무엇인가요?
A: PhoenixMiner can only detect the stale shares that were discovered after it has received a new job (i.e. the "very stale") shares. There is additional latency in the pool itself, and in the network connection, which makes a share stale even if it was technically found before the end of the block from the miner's point of view. As pools only reports the shares as accepted or rejected, there is no way for the miner to determine the stale shares from the pool's point of view.
Q006: 셰어를 찾았을 때 PhoenixMiner가 표시하는 "actual share difficulty"는
무슨 의미인가요?
A: It allows you to see how close you were to finding an actual block (a rare event these days for the most miners with reasonable-sized mining rigs). You can find the current difficulty for given coin on sites like whattomine.com and then check to see if you have exceeded it with your maximum share difficulty. If you did, you have found a block (which is what the mining is all about).
Q007: PhoenixMiner 통계에 표시되는 "effective speed"는 무슨 의미인가요?
A: This is a measure of the actually found shares, which determines how the pool sees your miner hashrate. This number should be close to the average hashrate of your rig (usually a 2-4% lower than it) depending you your current luck in finding shares. This statistic is meaningless in the first few hours after the miner is started and will level off to the real value with time.
Q008: 풀에 표시되는 유효 해시레이트가 PhoenixMiner에 표시되는 것보다 낮은 이유는 무엇인가요?
A: There are two reasons for this: stale shares and luck. The stale shares are rewarded at only about 50-70% by most pools. The luck factor should level itself off over time but it may take a few days before it does. If your effective hashrate reported by the pool is consistently lower than the hashrate of your rig by more than 5-7% than you should look at the number of stale shares and the average share acceptance time - if it is higher than 100 ms, try to find a pool that is near to you geographically to lower the network latency. You can also restart your rig, or try another pool.
문제 해결
P001: AMD RX470/480/570/580 또는 비슷한 그래픽카드를 사용하는데, 최근
몇 달 사이 Ethereum과 Ethereum classic 해시레이트가 크게 떨어졌습니다!
S: This is known problem with some cards. For the newer cards (RX470/480/570/580), this can be
solved by using the special blockchain driver from AMD (or try the latest drivers, they may
incorporate the fix). For the older cards there is no workaround but you still can mine EXP,
Musicoin, UBQ or PIRL with the same speed that you mined ETH before the drop.
P002: Nvidia GTX9x0 그래픽카드의 해시레이트가 Windows 10에서 매우 낮습니다!
S: While there is a (convoluted) workaround, the best solution is to avoid Windows 10
for these cards - use Windows 7 instead.
P003: Nvidia GTX970(또는 비슷한) 그래픽카드를 사용하는데 Ethereum 또는
Ethereum classic 해시레이트가 급격히 떨어졌습니다!
S: GTX970 has enough VRAM for larger DAGs but its hashate drops when the DAG size starts
to exceed 2 GB or so. Unlike the AMD Polaris-based cards, there is no workaround for this
problem. We recommend using these cards to mine EXP, Musicoin, UBQ or PIRL with the same speed
that you used to ETH before the drop.
P004: Windows 원격 데스크톱(RDP)을 사용할 때 일부 그래픽카드(또는 팬 속도와 온도)가 보이지 않습니다!
S: This is a known problem with RDP. Use VNC or TeamViewer instead.
P005: Windows 10에서 PhoenixMiner 콘솔 안을 클릭하면 멈춥니다!
S: This is a known problem on Windows 10, related to so called "Quick Edit" feature of the command
prompt window. From PhoenixMiner 2.6, the QuickMode is disabled by default, so you shouldn't experience
this problem. If you still, do, read here how to solve it: https://stackoverflow.com/q/33883530
P006: 시작 직후 PhoenixMiner가 작동을 멈추고 마지막 메시지가 "debugger detected"입니다
S: If you have only Nvidia cards, add the option -nvidia to the PhoenixMiner.exe command line.
If you have only AMD cards, add the option -amd to the command line.
P007: PhoenixMiner가 DAG 버퍼를 할당한 후 오류를 표시하고 종료됩니다.
S: If you have more than one GPU, make sure that your Windows page file minimal size is set to at
least (N x DS + 4) GB, where N is the number of GPUs, and DS is the size of DAG in GB (about 2.9 GB around
January 2019 for ETC and ETH). For example, if you have 10 GPUs, you need 10 x 2.9 + 4 = 33 GB minimal
size of the page file. Note that this will increase as the DAG sizes increase. If you are using -clkernel 3, for each GPU add size of
the DAG twice instead of once (e.g. for 3 GPUs mining with -clkenel 3 you will need 3 x 2 x 2.9 + 4 = 21.4 GB minimal page file size)
P008: DAG 에폭이 바뀔 때 마이너가 가끔 크래시됩니다.
S: During DAG generation, the GPUs are loaded more than during the normal operation. If you have
overclocked or undervolted the GPUs "to the edge", the DAG generation ofter pushes them "over the
edge". Another possible reason for the crash (especially if the whole rig crashes) is the higher
power usage during this process. You can lower the DAG generation speed by specifying the -lidag
command-line option. The possible values are 0 (no slow down), 1, 2, and 3 (max slowdown).
In order to check if your rig would be stable during DAG generation, run it in benchmark mode
by specifying the -bench 210 command line option. Then every time when you press the key 'd'
the miner will advance to the next DAG epoch, and you will be able to see if it is stable during
multiple DAG generations. If it isn't you can try to alter the -lidag and -eres command line options
until the desired stability is achieved.
P009: ETC 또는 ETH 채굴 시 마이너가 DAG 버퍼를 만들지 못합니다
S: The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. Both ETC and ETH has reached epoch 266 already. To ensure uninterrupted operation, please upgrade to 4.2.
PhoenixMiner 4.2 supports DAG epoch up to 330, and PhoenixMiner 4.5 supports DAG epoch up to 450.
