Bitcoin Forum
August 14, 2018, 06:48:23 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 120 »
  Print  
Author Topic: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)  (Read 80976 times)
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
December 26, 2017, 07:14:26 AM
Merited by suchmoon (5), Bojcha (1)
 #1

Changes in version 3.0c (since 2.9e):
  • Implemented auto-tune function which will find the best GT value for each GPU. You can activate it by either omitting the -gt parameter in the command line, or by pressing 'z' in the console. Note that auto-tune process takes about 3 to 5 minutes on average and during this time the hashrate will be lower and will go up and down. You can abort the auto-tuning by pressing the 'g' key in the console window.
  • Added support for 'x' key in console window. This will allow you to select a single GPU for manual or automatic GT tuning.
  • Added support for direct mining (without DAG switching for DevFee) of the following coins: Nekonium (NUKO), MIX, EtherGem (EGEM), AURA, Hotelbyte Coin (HBC), Genom (GEN), EtherZero (ETZ), Callisto   (CLO). See the -coin option documentation below for details how to specify the coin you are mining.
  • Added support for on-the-fly reload of config.txt file and applying the new options by pressing the key 'c' in the console window. Note that most options require restart in order to change. Currently the follwing options can be changed without restarting: -mi, -gt, -clf, -nvf, and all hardware control parameters (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc). This allows more convenient adjustment and fine-tuning of the mining rigs
  • Added -cdmrs option to reload the settings if config.txt is edited/uploaded by a remote manager. This allows you to change and reload the config.txt options via remote manager without access to the console window of the miner.
  • Small improvements in AMD kernels
  • Added -nvf 3 setting that could solve some problems with unstable Nvidia cards (but may affect hashrate negatively)
  • Added option -acm to turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console.
  • Added option -retrydelay that sets the pause between the reconnection attempts in seconds (min value 0, default value: 20)
  • Added option -resetoc to reset the HW overclocking setting on startup to their default values
  • Added option -gpureset, which forces full reset of the GPU when the miner is paused (or before DAG generation when switching DAG epochs). This is designed to avoid problems like the hashrate drop of GeForce GTX1080 Ti after pause/resume. This option can be specified per GPU and is turned on by default for GTX1080 Ti.
  • Added option -gser for serializing of DAG creation if your PSU(s) can't take all GPUs generating DAG simultaneously.
  • Graceful shutdown when closed by the close button of the console window (including reseting OC settings to defaults)
  • Added option -gsi to set the speed stats interval (5-30 seconds, default 5; 0 turns off the speed stats). The detailed stats are still shown every 45 seconds and aren't affected by the -gsi value
  • Fixed crashing with Vega cards with AMD drivers 18.4.1 and newer
  • Many small fixes and changes

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files with the notable exception of the dual mining feature (yet).

Please note that PhoenixMiner is extensively tested on many mining rigs but this is the
first public release and there still may be some bugs. Additionally, we are actively working on
bringing many new features in the future releases. If you encounter any problems or have
feature requests, please post them here (in this thread). We will do our best to answer in timely
fashion.

Screenshot:


1. Quick start

You can download PhoenixMiner 3.0c from here:

https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes:
Code:
   File: PhoenixMiner_3.0c.zip
   SHA-1: 490703702f6868c4862d7e5e36dd4a2150f06dee
 SHA-256: bd591a4e9d52df144ab789e797d0000717163032bf488708be3dff05817ae84b
 SHA-512: 02b4ac3d96824c7bfff9eb2e46ab2fa46ab67f0fa76a3801027bff13da90efc4da5a2f24f0b9d1076335fd8a24d6f3a07dbb133e22c35ff939170fb0812a9137

Here are the command line parameters for some of the more popular pools and coins:

ethermine.org (ETH):
  PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine.org (ETH, secure connection):
  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool.org (ETH):
  PhoenixMiner.exe -pool eu1.ethpool.org:3333 -pool2 us1.ethpool.org:3333 -wal YourEthWalletAddress.WorkerName -proto 3  
dwarfpool.com (ETH):
  PhoenixMiner.exe -pool eth-eu.dwarfpool.com:8008 -wal YourEthWalletAddress/WorkerName -pass x
nanopool.org (ETH):
  PhoenixMiner.exe -pool eu1.nanopool.org:9999 -wal YourEthWalletAddress/WorkerName -pass x
nicehash (ethash):
  PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
  PhoenixMiner.exe -epool eth.f2pool.com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName  
miningpoolhub (ETH):
  PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron.com (ETH):
  PhoenixMiner.exe -pool coinotron.com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine.org (ETC):
  PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal YourEtcWalletAddress.WorkerName
dwarfpool.com (EXP):
  PhoenixMiner.exe -pool exp-eu.dwarfpool.com:8018 -wal YourExpWalletAddress/WorkerName
miningpoolhub (MUSIC):
  PhoenixMiner.exe -pool europe.ethash-hub.miningpoolhub.com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
ubiqpool (UBIQ):
  PhoenixMiner.exe -pool stratum+tcp://eu.ubiqpool.io:8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
minerpool.net (PIRL):
  PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool.com (Metaverse ETP):
  PhoenixMiner.exe -pool etp.dodopool.com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass x
minerpool.net (Ellaism):
  PhoenixMiner.exe -pool ella.minerpool.net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x
etherdig.net (ETH PPS):
  PhoenixMiner.exe -pool etherdig.net:4444 -wal YourEthWalletAddress.WorkerName -proto 4 -pass x
etherdig.net (ETH HVPPS):
  PhoenixMiner.exe -pool etherdig.net:3333 -wal YourEthWalletAddress.WorkerName -proto 4 -pass x

2. Features, requirements, and limitations

* Supports AMD Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM
* Supports Nvidia 10x0 and 9x0 series as well as older cards with enough VRAM
* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed
* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)
* Advanced statistics: actual difficulty of each share as well as effective hashrate at the pool
* DAG file generation in the GPU for faster start-up and DAG epoch switches
* Supports all ethash mining pools and stratum protocols
* Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks
* Detailed statistics, including the individual cards hashrate, shares, temperature and fan speed
* Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)
* GPU tuning for the AMD GPUs to achieve maximum performance with your rig
* Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, and Metaverse ETP. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).
* Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.
* More features coming soon!

PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.). We are planning a Linux version in
the future but it may take some time.

PhenixMiner does not support dual mining. However we are working on this feature and will introduce it
soon. Solo mining is supported since version 2.7c.

While the miner is running, you can use some interactive commands. Press the key 'h' while the
miner's console window has the keyboard focus to see the list of the available commands. The
interactive commands are also listed at the end of the following section.

3. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore's miner.

Pool options:
  -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)
  -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
     pgc: Pegascoin
     akroma: Akroma
     whale: WhaleCoin
     vic: Victorium
     nuko: Nekonium
     mix: Mix
     egem: EtherGem
     aura: Aura
     hbc: Hotelbyte Coin
     gen: Genom
     etz: EtherZero
     clo: Callisto
  -stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no
  -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
General pool options:
  -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)
Benchmark mode:
  -bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
Remote control options:
  -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, -clf, -nvf, and all hardware control parameters
      (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).
Mining options:
  -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
  -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
  -clKernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative (1 is the default)
  -clNew <n> Use the new AMD kernels (0: no, 1: yes; default: 1)
  -clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1)
  -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.
  -list List the detected GPUs devices and exit
  -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
  -lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest). This option works only on AMD cards
  -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
  -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)
  -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.
  -timeout <n> Restart miner according to -rmode after n minutes
  -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
  -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
Hardware control options (most are for AMD cards only, only tt 0-4, tstop, and tstart are supported on Nvidia GPUs), use comma to specify different values for each 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 %)
  -fanmin <n> Set fan control min speed in % (-1 for default)
  -fanmax <n> Set fan control max speed in % (-1 for default)
  -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)
  -cvddc <n> Set GPU core voltage in mV (0 for default)
  -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)
General Options:
  -v,--version  Show the version and exit
  -h,--help  Show information about the command-line options and exit

Per-GPU options
Some of the PhoenixMiner options can provide either the same setting for all GPUs, or a different
setting for each of the GPUs. For example, to specify the -gt value for all cards you would write
-gt 90 but if you want to specify a different GT value for each of the cards, use something like this:
-gt 20,15,40,90,90 for a five-GPU mining rig. This would set GT to 20 for the first GPU, 15 for the second
GPU, and so on. If you specify less values than you have GPUs, the rest of the GPUs will use the default
value for the parameter.  
  
Additionally, while the miner is running, you can use the following interactive commands
in the console window by pressing one of these keys:
  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.)
  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  

4. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner's directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner's directory).

The advantages of using config.txt and epools.txt files are:
- If you have multiple rigs, you can copy and paste all settings with these files
- If you control your rigs via remote control, you can change pools and even the miner options by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
the miner.

5. Remote monitoring and management

Phoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore's dual miner,
including the "Remote manager" application that is part of Claymore's dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

6. Hardware control options

 Here are some important notes about the hardware control options:
  • If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values.
  • We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580 and Vega). Your results may vary with older GPUs.
  • The blockchain beta drivers from AMD show quite unstable results - often the voltages don't stick at all or revert back to the default after some time. For best results use the newest drivers from AMD: 18.1.1 or 18.2.1, where most of the bugs are fixed.
  • -tmax specifies the temperature at which the GPU should start to throttle (because the fans can't keep up).
  • If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner).
  • This should be obvious but still: if given clocks/voltages are causing crahses/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.
  • If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).

7. FAQ

Q001: Why another miner?
   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: Can I run several instances of PhoenixMiner on the same rig?
   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: Can I run PhoenixMiner simultaneously on the same rig with other miners?
   A: Yes, but see the answer to the previous question for how to avoid problems.
  
Q004: What is a stale share?
   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: Why is the percentage of stale shares reported by PhoenixMiner smaller than the one shown
   by the pool?
   A: PhonixMiner 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: What is the meaning of the "actual share difficulty" shown by PhoenixMiner when a share is
   found?
   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: What is the meaning of "effective speed" shown by PhoenixMiner's statistics?
   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: Why is the effective hashrate shown by the pool lower than the one shown by 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.

8. Troubleshooting

P001: I'm using AMD RX470/480/570/580 or similar card and my hashrate dropped significantly in the past
     few months for Ethereum and 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: My Nvidia GTX9x0 card is showing very low hashrate under 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: I'm using Nvidia GTX970 (or similar) card and my hashrate dropped dramatically for Ethereum or
      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: I can't see some of my cards (or their fan speed and temperature) when using Windows Remote Desktop (RDP)!
      S: This is a known problem with RDP. Use VNC or TeamViewer instead.
      
P005: On Windows 10, if you click inside the PhoenixMiner console, it freezes!
      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: Immediately after starting, PhoenixMiner stops working and the last message is "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 shows an error after allocating DAG buffer and shuts down.
      S: If you have more than one GPU, make sure that your Windows page file minimal size is set to at
     least 16 GB. If this doesn't help, start PhoenixMiner by running the start_miner.bat that is in the
     miner's folder. You MUST change the wallet address that is specified in start_miner.bat to make
     sure that the miner mines to your address. Also, make sure that all lines, starting with setx are
     not commented (i.e. they doesn't start with REM command).
     
P008: The miner sometimes crashes when the DAG epoch change.
      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 170 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.
1534272503
Hero Member
*
Offline Offline

Posts: 1534272503

View Profile Personal Message (Offline)

Ignore
1534272503
Reply with quote  #2

1534272503
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534272503
Hero Member
*
Offline Offline

Posts: 1534272503

View Profile Personal Message (Offline)

Ignore
1534272503
Reply with quote  #2

1534272503
Report to moderator
1534272503
Hero Member
*
Offline Offline

Posts: 1534272503

View Profile Personal Message (Offline)

Ignore
1534272503
Reply with quote  #2

1534272503
Report to moderator
1534272503
Hero Member
*
Offline Offline

Posts: 1534272503

View Profile Personal Message (Offline)

Ignore
1534272503
Reply with quote  #2

1534272503
Report to moderator
xiekang12121
Jr. Member
*
Offline Offline

Activity: 31
Merit: 0


View Profile
December 26, 2017, 10:45:06 AM
 #2

Completely remove the developer's expense version,
Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner NoDevFee v10.3
https://bitcointalk.org/index.php?topic=2645690.0
syraka76
Member
**
Offline Offline

Activity: 83
Merit: 10

I AM MARVYKKIO


View Profile
December 26, 2017, 11:41:47 AM
 #3

hello, the most important information is missing,
1) screenshot
2) speed
3) AMD support, nvidia?

 Huh

Thanks to the administrators I lost the account
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
December 26, 2017, 12:58:12 PM
 #4

Hello!

  Sorry for the missing info:

  1. Screenshot from mining rig with 5 GPUs (2 AMD RX480, 2 AMD RX570 and 1 GTX1070 - note that the cards are optimized for power consumption on this rig because here the electricity is rather expensive):

    

  2. The speed is generally slightly faster than Claymore's Ethereum miner in eth only mode (we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed interactively with the + and - keys while the miner is running). Of course, you don't have to believe us, and should check for yourself.

  3. It is mentioned in the first post that the miner supports all modern AMD and Nvidia cards like AMD RX480/470/580/570, Vega, RX460/560, and Nvidia GTX9x0 and GTX10x0. Older AMD and Nvidia cards are also supported if they have at least 2 GB VRAM (for coins other than ETH and ETC) or 4 GB VRAM (for all coins).

I want to buy your program, please give me your Skype

   Unfortunately, the miner is not for sale, it is free to use with the devfee of 0.65%, which we think is very reasonable.

  PhoenixMiner team
santan
Member
**
Offline Offline

Activity: 105
Merit: 11


View Profile
December 26, 2017, 01:14:37 PM
 #5

I tried your miner ..... using my Quadro K2100M..... with 2GB VRAM and 3CU
but it says.........

NVML library initialized
FATAL ERROR: Debugger detected


Why is that ??
danialzo
Jr. Member
*
Offline Offline

Activity: 84
Merit: 0


View Profile
December 26, 2017, 01:19:12 PM
 #6

Great that there developers out there trying to build a competition to profit both developers and users. In my personal opinion, having a roughly 1% higher hash rate (which you are not sure nor promote strongly) and offering 0.3% lower rate won't attract many users.
Claymore has gained so much popularity and credit which won't let the users bother trying a new miner program, unless it is way faster, better, feature-rich.

There are so many obstacles for your miner program to enter the competition, like trust, benefit, speed, stability, feature, and ...
syraka76
Member
**
Offline Offline

Activity: 83
Merit: 10

I AM MARVYKKIO


View Profile
December 26, 2017, 01:42:19 PM
 #7

first of all claymore would be even now to lower his devfee, especially on the miner 12.6 equiash, which still the devfee is high, and lasts 90 seconds.
in my opinion it is right that there is a lot of competition, if the miner of this boy is faster than only 1% compared to claymore or other miners, considering the devfee 0.65% and more gain for us miners.
the question is: and clean this miner? are we sure that it does not hide anything illegal to steal coins and empty the customer wallets?
for the rest if it is clean and deserves, well come.

Thanks to the administrators I lost the account
syraka76
Member
**
Offline Offline

Activity: 83
Merit: 10

I AM MARVYKKIO


View Profile
December 26, 2017, 01:47:17 PM
 #8

https://www.virustotal.com/#/file/c0f6ff3dc366de7c4a908fcfcd7d0482352ceee9f6add1a272c1afa6f6358a7f/detection



the program is as clean as water

Thanks to the administrators I lost the account
danialzo
Jr. Member
*
Offline Offline

Activity: 84
Merit: 0


View Profile
December 26, 2017, 01:50:02 PM
 #9


you mean the .bat file is clean as water?! Grin
k0stas
Hero Member
*****
Offline Offline

Activity: 512
Merit: 500


View Profile WWW
December 26, 2017, 01:51:28 PM
 #10

You thought many hours for the name of the miner? Cheesy

syraka76
Member
**
Offline Offline

Activity: 83
Merit: 10

I AM MARVYKKIO


View Profile
December 26, 2017, 02:03:34 PM
 #11



file .exe

Thanks to the administrators I lost the account
danialzo
Jr. Member
*
Offline Offline

Activity: 84
Merit: 0


View Profile
December 26, 2017, 02:12:48 PM
 #12


dude! look at top section of the report! it clearly says .bat with size of 615B ! Read the report details
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
December 26, 2017, 04:25:13 PM
 #13

the question is: and clean this miner? are we sure that it does not hide anything illegal to steal coins and empty the customer wallets?
for the rest if it is clean and deserves, well come.
We can guarantee that the executables are 100% clean. We even decided to avoid packing the executable to allow better inspection by the anti-virus programs. Still, there is always some chance that an over-aggressive anti-virus program will give you a false positive but you can safely ignore it. As an additional precaution you can check if the .zip archive you have downloaded has the right checksum (the checksums are listed in text file PhoenixMiner_2.1_checksums.txt, which is in the MEGA folder from the first post in this thread).

You thought many hours for the name of the miner? Cheesy
Point taken Wink Still, we thought that our time is best spent trying to improve the mining performance instead of trying to come up with a cool name Smiley

In my personal opinion, having a roughly 1% higher hash rate (which you are not sure nor promote strongly) and offering 0.3% lower rate won't attract many users.
While 1% or so may seem too little to matter, the hard truth about mining is that you have to pay your electricity bill and the amortization costs of the hardware, so the real ROI is often less than 20% per year. In this context 1% is quite welcome. Of course, if you keep your earnings in crypto and hope that it will go up, it may be a lot more than that but this is a risk that a lot of miners can't or won't take.

I tried your miner ..... using my Quadro K2100M..... with 2GB VRAM and 3CU
but it says.........

NVML library initialized
FATAL ERROR: Debugger detected


Why is that ??

This means that anti-dubugger code is kicking in. Probably you have some kind of CUDA profiler or debugger running and PhoenixMiner is terminating to avoid reverse engineering. At any rate we haven't tested Quadro cards (and their drivers) as they are not very often used for mining.

PhoenixMiner team
santan
Member
**
Offline Offline

Activity: 105
Merit: 11


View Profile
December 26, 2017, 04:44:02 PM
 #14

I tried your miner ..... using my Quadro K2100M..... with 2GB VRAM and 3CU
but it says.........

NVML library initialized
FATAL ERROR: Debugger detected


Why is that ??

This means that anti-dubugger code is kicking in. Probably you have some kind of CUDA profiler or debugger running and PhoenixMiner is terminating to avoid reverse engineering. At any rate we haven't tested Quadro cards (and their drivers) as they are not very often used for mining.

PhoenixMiner team
I know Quadro cards are not suitable for mining but i can run ccminer almost all algo and siaminer in it with no issue. However i have not yet run any Ethash based miner. I thought your's would be the first .... but no luck.

Regarding debugger, i don't have any on it. I do have CUDA 8 Toolkit which i use with compute 3.0 and drivers version is 377.48.
Anyway ... see if it is something very easy to spot and correct for you.......... otherwise you can safely ignore....

Do have any plan to show the found Nonce in your miner.
TeppiVietNam
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
December 27, 2017, 01:38:38 AM
 #15

After download, the antivirus show file has virus....
preda
Sr. Member
****
Online Online

Activity: 448
Merit: 250



View Profile
December 27, 2017, 01:53:08 AM
 #16

very instersting... but i will lurk and watch people testing it and make sure this program is safe then i will try and i will support you.
thanks anyway for the great job!

                 ░▒▓▓▓▓▓▓▓▓▓▒▒░
           ░▒█████████████████████▒░
         ▓███████████████████████████▓░
      ░███████████████▓░▒███████████████░
     ▓██████████▓▓▒░        ▒▒▓▓██████████
   ░███▓                               ▒███▒
  ░████               ▒▒▒               ████▒
 ░█████░           ░███████░            █████▒
 ██████░          ░██      ██▒          ██████
░██████░          ██       ██           ██████▒
▓██████           ██░ ░   ░██           ███████
▓██████         ████████████████        ███████
▓██████        █████████████████        ███████
░██████▒       ███████████████       ░██████▓
 ███████       █████████████████       ▓██████
 ░███████       ████████████████      ▓██████▒
  ▒███████▒       ░ ░     ░ ░       ░███████▒
   ░████████▒                     ▒████████▒
     ▓████████▓░               ░▓█████████
      ░██████████▓░          ▓██████████░
         ▓██████████▒     ▒██████████▓░
           ░▒██████████▒▓█████████▓░
                 ░▒▓▓▓▓▓▓▓▓▓▒▒░
danialzo
Jr. Member
*
Offline Offline

Activity: 84
Merit: 0


View Profile
December 27, 2017, 02:35:52 AM
 #17

After download, the antivirus show file has virus....
We need some security experts with good level of trust to dig in and verify this otherwise the developers could always come back and say "hey it is safe, the antivirus is paranoid"
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
December 27, 2017, 07:13:43 AM
 #18

After download, the antivirus show file has virus....

We can guarantee that the file is clean but there may be some anti-virus programs that doesn't like it. We have tried all the major ones and they do not find anything. The .exe is not packed but it contains some code to detect if debugger or profiler is attached to try and debug and reverse it. In such case PhoenixMiner just exits.

Regarding debugger, i don't have any on it. I do have CUDA 8 Toolkit which i use with compute 3.0 and drivers version is 377.48.
Anyway ... see if it is something very easy to spot and correct for you.......... otherwise you can safely ignore....

Unfortunately we don't know why this is happening so there is no easy way to fix it. It shouldn't be the CUDA toolkit as it is installed on all of our development machines and it doesn't interfere with PhoenixMiner.

Do have any plan to show the found Nonce in your miner.

As you can see on the screenshot from the first post  (you can also see it here: ), we print the difficulty to each found share and also the maximum difficulty of any found share. The nonce itself can be seen in the log file but it is not very interesting as what it matters is the difficulty of the found share. If it is bigger than the current difficulty of the coin that you mine, you have found a block! For example for Pirl the current difficulty is about 9.8 TH and the screenshot shows that the maximum difficulty of found share is 14.3 TH, so at least one block as found in the current mining session.
santan
Member
**
Offline Offline

Activity: 105
Merit: 11


View Profile
December 27, 2017, 10:13:40 AM
 #19

Yes you are correct the difficulty is the most important if i am trying to solve a block.... and i am glad that your miner has it shown, Nobody could convince claymore to print it. (also i took "-log 2", nice!! you had it!).

And for a side note i tested finally your miner on my 1080Ti card and it is indeed a little bit faster than Claymore at same setting .....giving 35.3 MH/s.... plus your's devfee is less. Smiley
weoihr
Newbie
*
Offline Offline

Activity: 5
Merit: 1


View Profile
December 28, 2017, 06:05:08 AM
Merited by vapourminer (1)
 #20

Well, I'm not sure I qualify as "security expert" but I certainly am a "full-time security paranoic"  Grin And as no one else seem to risk it, I downloaded and tested the miner as well as I could.

First, I used an online virus scanner to check the file.
The results are: 2/67 detected (https://www.virustotal.com/#/file/74cfd6a34e158c2f5fe1b8422d6b8daee304394eeaf85992b117bf5de315d569/detection), which is actually an excellent result, given that the Claymore's miner gives 41/68 positives (https://www.virustotal.com/#/file/7852c50c835d7110ab8d055cccad06674e94d85324414f91366852bed9be29cc/detection).

And even the open-source ethminer 0.12.0 gives 26/67 positives, which is ridiculous (https://www.virustotal.com/#/file/4aa1082b5581540eced3acb18ee52cd06ee062772a5d386cf7501b2a8b7af094/detectionHuh

So, I prepared a backup image of the SSD of my rig (in case that this new miner turn out to be malicious) and then ran it for about 18 hours while monitoring the PhoenixMiner.exe network, file system, and registry activity with Wireshark and some advanced system calls monitors. It connected to my mining pool as it should and then opened port 3333, which turned out to be the port for remote control similar to Claymore's miner. I disabled to remote port with the "-cdm 0" commnad-line switch and restarted the miner. Sure enough, this time port 3333 wasn't opened and the only connection was the one to my pool.

The first new connection was observed after 16 minutes of mining, which connected to another pool (ehtermine.org) and the miner showed that it was mining for developer fee. It disconnected after 35 seconds as advertised. After that I left the rig alone and analyzed the Wireshark and the other logs the next day.

The miner connected to the devfee pool every 90 minutes, with one exception when it wasn't able to connect to the ehtermine.org. It then tried again after 13 minutes and then resumed the normal 90 minutes period between devfee connections. No other network activity was recorded. The registry activity was also normal (no keys were created and no suspicious registry key reading was detected). Also, no files outside the current folder were opened or touched.

As for the mining speed, my rig has 6x ASUS Strix 570 OC (with BIOS mod) and under Claymore's miner it makes about 173 mhs. With Phoenix the speed was about 174.5 mhs, which is not much better but I guess is still something. The power consumption from the wall was about the same (755-765W). According the the pool, the speed was even better (169 vs 166 with claymore) but this doesn't mean much as I've seen this numbers change a lot without any apparent reason, so it would take some more time before declaring PhoenixMiner to be faster.

Of course, there is no guarantee that the PhoenixMiner won't "decide to go bad" at some point of the future, but right now it seems legit.  Cool

Some suggestions for the devs: the share difficulty is a nice touch but it would be better to directly show the number of blocks found. Most pools doesn't report this and even when they do, I'm always suspicions. Also, your miner does seem to be compatible with Claymore's manager, which is nice, but I hope that you will produce a better manager (and maybe even a mobile app for Android), because the claymore's manager is rather simplistic and I miss a lot of features.
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 120 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!