PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[Faizrakhmanov]

Hi! Do I need to restart miner when I send new config.txt through Remote Manager or it applies automatically the moment i sent it?

Hi. If you send remotely new config file miner start work with this new config. Additional miner reboot not needed.

[peoples]

@PhoenixMiner

can you explain how you create nonce ? Is it randomized, and how u randomize ?

Thanks

[jorm_11]

Hey fellas, see if anyone can help. I've been running a 4 GPUs set up for more than a year, and just this week out of the blue I got this error:

Code:

2019.04.14:13:41:02.645: main Phoenix Miner 4.2c Windows/msvc - Release build
2019.04.14:13:41:03.767: main CUDA version: 9.0, CUDA runtime: 8.0
2019.04.14:13:41:03.809: main No OpenCL platforms found
2019.04.14:13:41:03.810: main Available GPUs for mining:
2019.04.14:13:41:03.810: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2019.04.14:13:41:03.810: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2019.04.14:13:41:03.810: main GPU3: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2019.04.14:13:41:03.824: main NVML library initialized
2019.04.14:13:41:03.854: main NVML error in CudaProgram.cu:147 : GPU is lost (15)
2019.04.14:13:41:03.854: main NVML error in CudaProgram.cu:150 : Invalid Argument (2)
2019.04.14:13:41:03.872: main Nvidia driver version: 391.01

I thought it was a hardware issue, but nope. Everything is working fine (I replaced risers/cables, etc.). I have to unplug all GPUs in order to get the mobo to recognize all of them again. Any ideas? Thanks

[jorm_11]

Ok so I might have found the issue. Check this, I'm using a single SATA from the PSU to power up a riser; it turns out the pins of the connector are rusted, and that's why it was losing power intermittently. So I just connected the GPU in question to my server PSU, and voila.

[PhoenixMiner]

I got tripped up by this in the past - luckily realized the problem way before getting to the point of suspicion.  But still need to remember every release or new rig setup to comment out epools, since I always use config exclusively.

Might be worth rethinking this design...  one possible solution would be two different 'pool' flags - maybe '--pool' behavior ignores epools, while '--addpool' follows the current behavior?

   We will rename the sample epools.txt file to something else to avoid future problems like this.

PhoenixMiner, extremely need -tt function in Linux. Please HEPL.

   We are working on this, hopefully it will make it in the next release.

Hi! Do I need to restart miner when I send new config.txt through Remote Manager or it applies automatically the moment i sent it?

   If you have specified the command-line option -cdmrs some of the options are applied without restart. The full list is in the description of the -cdmrs option in the first post of this forum thread:

  -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, and all hardware control parameters
      (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).

@PhoenixMiner

can you explain how you create nonce ? Is it randomized, and how u randomize ?

Thanks

   It is randomized and different (independent) for each GPU. The exact random algorithm doesn't matter as long as it has good distribution.

Ok so I might have found the issue. Check this, I'm using a single SATA from the PSU to power up a riser; it turns out the pins of the connector are rusted, and that's why it was losing power intermittently. So I just connected the GPU in question to my server PSU, and voila.

   It would be nice to have clear error messages from the GPUs when the 12V power is missing or unstable but unfortunately the GPU doesn't report such events.

[PhoenixMiner]

Important message for everyone that is running older versions of PhoenixMiner (before 4.2):

IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. ETC will reach epoch 266 in about 20 days, and ETH will reach epoch 266 in about two months. To ensure uninterrupted operation, please upgrade to 4.2 before epoch 266. If you are mining other coins, you can safely disregard this message.

The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly in the future releases.

[GKumaran]

Results:
Cards : Vega 64 (aircooled, reference, samsung)
Platform : Windows 10, 18.6.1
Miner : PheonixMiner 4.2c
Algo : Ethash
Clocks : 1216/1107/875 (ODT)
Actual : 1187/1107/850 (HWinfo)

Stock                                                                                                                                                           : 44.75 mh/s
Current Timing  --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600       : 50.12 (12% inc over stock)

Finally broke the Ethash 50mh/s barrier in windows 

https://bitcointalk.org/index.php?topic=5123724.msg50615480#msg50615480

[bategojko74]

Results:
Cards : Vega 64 (aircooled, reference, samsung)
Platform : Windows 10, 18.6.1
Miner : PheonixMiner 4.2c
Algo : Ethash
Clocks : 1216/1107/875 (ODT)
Actual : 1187/1107/850 (HWinfo)

Stock                                                                                                                                                           : 44.75 mh/s
Current Timing  --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600       : 50.12 (12% inc over stock)

Finally broke the Ethash 50mh/s barrier in windows  

https://bitcointalk.org/index.php?topic=5123724.msg50615480#msg50615480

Unbeliavable, here they make just 46 using all available on the net miners:
https://minermonitoring.com/benchmark/Radeon+RX+Vega?software=&algo=ethash&type=&sort=-hashrate

[triedthisname]

Doing good Radeon 92 mhs VII http://prntscr.com/ncxvsi

[hustleman]

Can VBK be dual mined with PHX?

[Branko]

Doing good Radeon 92 mhs VII http://prntscr.com/ncxvsi

Its great card, but for same money here I can buy full 6xRX580 rig here

[mrplow]

Hi, thank you very much for this great program. Last night I uninstalled amdgpu-pro then upgraded from Ubuntu 16.04 to 18.04. I then install amdgpu-pro 18.40-697810 with the --opencl=legacy command line option.

I'm now getting the 'Unknown OpenCL driver version' message while running phoenix in dual mode, eth and blake2s.

If I run it with -clKernel 0 I can mine eth but then no dual support.

Sorry if I'm missing something obvious but the search for this forum leaves much to be desired.

Code:

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

No CUDA driver found
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2686.5)
Available GPUs for mining:
GPU1: AMD Radeon (TM) R9 Fury Series (pcie 1), OpenCL 1.2, 4 GB VRAM, 64 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: eth-us-west1.nanopool.org:9999
Dual: Loading pools from dpools.txt
B2S: the pool list contains 1 pool (1 from command-line)
B2S: primary pool: blake2s.usa.nicehash.com:3361
Starting GPU mining
Eth: Connecting to ethash pool eth-us-west1.nanopool.org:9999 (proto: EthProxy)
B2S: Connecting to blake2s pool blake2s.usa.nicehash.com:3361 (proto: Stratum)
B2S: Connected to blake2s pool blake2s.usa.nicehash.com:3361 (172.65.194.244)
Eth: Connected to ethash pool eth-us-west1.nanopool.org:9999 (66.42.105.146)
B2S: Subscribed to blake2s pool
B2S: Worker [redacted] authorized
B2S: New job #[redacted] from blake2s.usa.nicehash.com:3361; diff: 137.4GH
Listening for CDM remote manager at port 3333 in read-only mode
GPU1: 30C 14%
Eth: New job #[redacted] from eth-us-west1.nanopool.org:9999; diff: 10000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #253
Light cache generated in 2.5 s (19.2 MB/s)
GPU1: Allocating DAG (2.99) GB; good for epoch up to #255
GPU1: Generating DAG for epoch #253
GPU1: DAG  17%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG  34%
GPU1: DAG  50%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG  67%
GPU1: DAG  84%
GPU1: DAG 100%
GPU1: DAG generated in 10.5 s (290.4 MB/s)
GPU1: Failed to prepare kernels: clCreateKernel (-46)
Thread(s) not responding. Restarting.

Code:

sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: Fiji [Radeon R9 FURY / NANO Series]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: c8
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:35 memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:e000(size=256) memory:fea00000-fea3ffff memory:c0000-dffff

Code:

cat config.txt
-epool eth-us-west1.nanopool.org:9999
-ewal [redacted]
-epsw x

-dpool stratum+tcp://blake2s.usa.nicehash.com:3361
-dwal [redacted]
-dpsw x
-dcoin blake2s

[allur]

It is a fast miner, but has unpleasant issue: if during mining you loose internet connection - phoenix continues to mine! Shows "disconnected from pool", but gpus are loaded, and rig consumes power with no result. No good..
Tried ver.3.5 and new 4.2 - the same problem.
Claymore in same situation stops mining and release gpu load, so electricity not wasted.

[tipo70]

Tonight, stopped mining on RX 550 2 gb.

2019.04.19:11:22:10.878: main Eth: Mining MOAC on >moac.2miners.com:5050 for 0:00
2019.04.19:11:22:10.878: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.04.19:11:22:10.878: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.04.19:11:22:10.878: main Eth: Average speed (5 min): 0.000 MH/s
2019.04.19:11:22:10.878: main  
2019.04.19:11:22:21.724: main GPU1: 34C 39%, GPU2: 34C 39%, GPU3: 37C 39%, GPU4: 37C 39%, GPU5: 40C 39%, GPU6: 40C 24%, GPU7: 46C 33%, GPU8: 52C 35%, GPU9: 49C 34%, GPU10: 40C 24%, GPU11: 42C 16%, GPU12: 31C 30%
2019.04.19:11:22:26.811: unkn Eth: Connecting to ethash pool moac.2miners.com:5050 (proto: EthProxy)
2019.04.19:11:22:26.889: eths Eth: Connected to ethash pool moac.2miners.com:5050 (54.36.109.4)
2019.04.19:11:22:26.889: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":[""]}

2019.04.19:11:22:26.969: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.04.19:11:22:26.969: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.04.19:11:22:27.051: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":
2019.04.19:11:22:27.051: eths Eth: New job #e9614ac8 from moac.2miners.com:5050; diff: 8600MH
2019.04.19:11:22:27.051: eths GPU1: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU2: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU3: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU4: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU5: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU6: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU7: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU8: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU9: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU10: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU11: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU12: not enough VRAM for DAG epoch 77

[dierickxalexandre@gmail.c]

hello whats the arguments to add the flag nvidia to the GPU1 and amd to the rest?

[deskless]

Can we have Rx 570 and Radeon VII on the same rig to mine Ethereum?

[bategojko74]

Can we have Rx 570 and Radeon VII on the same rig to mine Ethereum?

Definitely yes. As far as your driver supports Radeon VII it will also support Rx 570. Choose a driver before 19.4.1 supporting Radeon VII so Phoenix miner supports it too.

[Bohr256]

Any idea what could be causing this:

NVML error inCudaProgram.cu:150 Invalid Argument GPU is lost(15)
NVML error inCudaProgram.cu:150 Invalid Argument (2)

Just saw this today. It was working fine for months.

I unplugged/replaced everything like in 10x different combos before and wouldn't work. Now it works? Let's see how long it will run lol.

[Digital_Seytan]

It is a fast miner, but has unpleasant issue: if during mining you loose internet connection - phoenix continues to mine! Shows "disconnected from pool", but gpus are loaded, and rig consumes power with no result. No good..
Tried ver.3.5 and new 4.2 - the same problem.
Claymore in same situation stops mining and release gpu load, so electricity not wasted.

https://latest-miners.wixsite.com/latestminer

yes PM developer, this is correct please find a solution for this problem in the next update, this is really wasted energy if there is no connection and phoenixminer runs at full speed for nothing until the internet connection returns

[PhoenixMiner]

Hi, thank you very much for this great program. Last night I uninstalled amdgpu-pro then upgraded from Ubuntu 16.04 to 18.04. I then install amdgpu-pro 18.40-697810 with the --opencl=legacy command line option.

I'm now getting the 'Unknown OpenCL driver version' message while running phoenix in dual mode, eth and blake2s.

If I run it with -clKernel 0 I can mine eth but then no dual support.

Sorry if I'm missing something obvious but the search for this forum leaves much to be desired.

Code:

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

No CUDA driver found
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2686.5)
Available GPUs for mining:
GPU1: AMD Radeon (TM) R9 Fury Series (pcie 1), OpenCL 1.2, 4 GB VRAM, 64 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: eth-us-west1.nanopool.org:9999
Dual: Loading pools from dpools.txt
B2S: the pool list contains 1 pool (1 from command-line)
B2S: primary pool: blake2s.usa.nicehash.com:3361
Starting GPU mining
Eth: Connecting to ethash pool eth-us-west1.nanopool.org:9999 (proto: EthProxy)
B2S: Connecting to blake2s pool blake2s.usa.nicehash.com:3361 (proto: Stratum)
B2S: Connected to blake2s pool blake2s.usa.nicehash.com:3361 (172.65.194.244)
Eth: Connected to ethash pool eth-us-west1.nanopool.org:9999 (66.42.105.146)
B2S: Subscribed to blake2s pool
B2S: Worker [redacted] authorized
B2S: New job #[redacted] from blake2s.usa.nicehash.com:3361; diff: 137.4GH
Listening for CDM remote manager at port 3333 in read-only mode
GPU1: 30C 14%
Eth: New job #[redacted] from eth-us-west1.nanopool.org:9999; diff: 10000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #253
Light cache generated in 2.5 s (19.2 MB/s)
GPU1: Allocating DAG (2.99) GB; good for epoch up to #255
GPU1: Generating DAG for epoch #253
GPU1: DAG  17%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG  34%
GPU1: DAG  50%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG  67%
GPU1: DAG  84%
GPU1: DAG 100%
GPU1: DAG generated in 10.5 s (290.4 MB/s)
GPU1: Failed to prepare kernels: clCreateKernel (-46)
Thread(s) not responding. Restarting.

   The current version of PhoenixMiner 4.2c supports AMD Linux drivers up to 18.40-676022 (your driver is the next one and is not supported by the released version). You need to uninstall amdgpu-pro and then download and install the 18.40-676022 drivers. We will add support for all newer drivers in the next release of PhoenixMiner but obviously nothing stops AMD from releasing newer drivers after that and therefore we recommend to avoid upgrading to drivers that are newer than the version of the PhoenixMiner you are using.

It is a fast miner, but has unpleasant issue: if during mining you loose internet connection - phoenix continues to mine! Shows "disconnected from pool", but gpus are loaded, and rig consumes power with no result. No good..
Tried ver.3.5 and new 4.2 - the same problem.
Claymore in same situation stops mining and release gpu load, so electricity not wasted.

  Give it 3-4 minutes and it will stop mining. We don't immediately stop mining to avoid crashing if the connection is soon restored.

Tonight, stopped mining on RX 550 2 gb.

Code:

2019.04.19:11:22:10.878: main Eth: Mining MOAC on >moac.2miners.com:5050 for 0:00
2019.04.19:11:22:10.878: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.04.19:11:22:10.878: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.04.19:11:22:10.878: main Eth: Average speed (5 min): 0.000 MH/s
2019.04.19:11:22:10.878: main 
2019.04.19:11:22:21.724: main GPU1: 34C 39%, GPU2: 34C 39%, GPU3: 37C 39%, GPU4: 37C 39%, GPU5: 40C 39%, GPU6: 40C 24%, GPU7: 46C 33%, GPU8: 52C 35%, GPU9: 49C 34%, GPU10: 40C 24%, GPU11: 42C 16%, GPU12: 31C 30%
2019.04.19:11:22:26.811: unkn Eth: Connecting to ethash pool moac.2miners.com:5050 (proto: EthProxy)
2019.04.19:11:22:26.889: eths Eth: Connected to ethash pool moac.2miners.com:5050 (54.36.109.4)
2019.04.19:11:22:26.889: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":[""]}

2019.04.19:11:22:26.969: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.04.19:11:22:26.969: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.04.19:11:22:27.051: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":
2019.04.19:11:22:27.051: eths Eth: New job #e9614ac8 from moac.2miners.com:5050; diff: 8600MH
2019.04.19:11:22:27.051: eths GPU1: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU2: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU3: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU4: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU5: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU6: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU7: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU8: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU9: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU10: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU11: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU12: not enough VRAM for DAG epoch 77

   Add the following options: -rvram -1 -eres 0   This will stop the check for minimum free VRAM and will not allocate bigger DAG buffer than necessary for the future DAG epochs.

hello whats the arguments to add the flag nvidia to the GPU1 and amd to the rest?

   It's not quite clear what you are trying to achieve. If you are referring to the -nvXXX and -clXXX flags, they are only applied to the respective types of GPUs. If you want the same value for all AMD GPUs, just use a single value like: -clkernel 2 which will set this for all AMD GPUs and won't affect the Nvidia GPUs at all. If want to achieve something else, please let us know to give more clear answer.