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

[Aurren]

On HiveOS as well, was getting the same problem, and then I tried -gser 2, and that was able to initialize the first 5 cards until the miner detected that my other 3 cards (all NVIDIA 1060 3gb) was unresponsive and it restarted the miner again, then it just keeps going in that loop of creating the DAG for 5 cards and restarting the miner.  Is there a way to delay the miner from checking the cards until the -gser 2 has a chance to create the DAG for all the cards?

EDIT:  I also want to add that the current HiveOS startup for claymore can load the DAG for all 8 cards all at once.

  Please try using the -gser 1 option, or turn off the watchdog with -wdog 0 and see if this fixes the problem. We will make changes in the next release but it is important to know what is happening to avoid the problem in the future.

I can report that -gser 1 doesn't work, it tries to generate DAG for the first three cards but stuck at 0%.  I can also report that -wdog 0 works and the miner runs fine, it took about 2-3 minutes to fully generate DAG for all 8 cards.  I really don't want the watchdog to be disabled though, but I can at least report it works in HiveOS with -gser 2 and -wdog 0, on 8 1060 3GB cards.

EDIT:  Also, new problem is that Hive doesn't see the current hashrate.  My current miner options are: "-nvidia -leaveoc -gser 2 -wdog 0".  It reports to the pool just fine, but in HiveOS it sees temperature and fan speed but not hashrate.

  Thank you this is useful information. If you are able it would be very helpful if you send us the log from the first few minutes (up to the point where the DAGs are created and the miner is already working) from a successful run with "-nvidia -leaveoc -gser 2 -wdog 0". We need to know if the problem is with slow creation of the light cache, or with some kind of DAG buffer allocation problems with the GPUs themselves.
  
   As for the HiveOS not reporting the hashrate - this seems to be intermittent problem with HiveOS itself, it worked fine most of the time but sometimes it wouldn't refresh the hashrate by itself (on the stats graph) but it would show as numbers on the top of the miner status page.

Code:

2018.10.01:11:47:06.282: main Phoenix Miner 3.5d Linux/gcc - Release build
2018.10.01:11:47:06.282: main Cmd line:
2018.10.01:11:47:06.282: main config.txt: -logfile /var/log/miner/phoenixminer/phoenixminer.log -nvidia -leaveoc -gser 2 -wdog 0
2018.10.01:11:47:06.480: main Available GPUs for mining:
2018.10.01:11:47:06.480: main GPU1: GeForce GTX 1060 3GB (pcie 1), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU2: GeForce GTX 1060 3GB (pcie 2), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU3: GeForce GTX 1060 3GB (pcie 3), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU4: GeForce GTX 1060 3GB (pcie 4), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU5: GeForce GTX 1060 3GB (pcie 5), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU6: GeForce GTX 1060 3GB (pcie 6), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU7: GeForce GTX 1060 3GB (pcie 8), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.480: main GPU8: GeForce GTX 1060 3GB (pcie 9), CUDA cap. 6.1, 2.9 GB VRAM, 9 CUs
2018.10.01:11:47:06.482: main NVML library initialized
2018.10.01:11:47:06.537: main Eth: the pool list contains 1 pool
2018.10.01:11:47:06.537: main Eth: primary pool: ssl://us2.ethermine.org:5555
2018.10.01:11:47:06.537: main Starting GPU mining
2018.10.01:11:47:06.538: main Eth: Connecting to ethash pool ssl://us2.ethermine.org:5555 (proto: QtMiner)
2018.10.01:11:47:06.636: eths Eth: Connected to SSL ethash pool us2.ethermine.org:5555 (52.37.202.243)
2018.10.01:11:47:06.738: main Listening for CDM remote manager at port 3333 in read-only mode
2018.10.01:11:47:06.739: main GPU1: 44C 61%, GPU2: 46C 4%, GPU3: 43C 61%, GPU4:48C 8%, GPU5: 38C 58%, GPU6: 49C 13%, GPU7: 42C 60%, GPU8: 51C 19%
2018.10.01:11:47:06.815: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["REDACTED"]}

2018.10.01:11:47:06.894: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.10.01:11:47:06.894: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.10.01:11:47:06.981: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x72dd5275e5100bbbb0d5db3768a12362f1009e4cbbae58b65ca837d4f48dc376","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622ee8"]}
2018.10.01:11:47:06.981: eths Eth: New job #72dd5275 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:06.982: GPU1 GPU1: Starting up... (0)
2018.10.01:11:47:06.983: GPU1 Eth: Generating light cache for epoch #214
2018.10.01:11:47:11.550: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:11.550: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:12.989: GPU1 GPU1: Allocating DAG (2.69) GB; good for epoch upto #216
2018.10.01:11:47:12.998: GPU1 GPU1: Allocating light cache buffer (43.0) MB; good for epoch up to #216
2018.10.01:11:47:13.109: GPU1 GPU1: Generating DAG for epoch #214
2018.10.01:11:47:14.810: GPU1 GPU1: DAG  12%
2018.10.01:11:47:15.489: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x31297a68fdcaa83fc1d28ebe2d1b120f8c2d105a90a6e1bce93272843c6439cf","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622ee9"]}
2018.10.01:11:47:15.489: eths Eth: New job #31297a68 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:16.505: GPU1 GPU1: DAG  28%
2018.10.01:11:47:16.562: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:16.562: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:16.815: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.10.01:11:47:16.900: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x31297a68fdcaa83fc1d28ebe2d1b120f8c2d105a90a6e1bce93272843c6439cf","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622ee9"]}
2018.10.01:11:47:18.202: GPU1 GPU1: DAG  44%
2018.10.01:11:47:19.898: GPU1 GPU1: DAG  59%
2018.10.01:11:47:21.575: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:21.575: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:21.595: GPU1 GPU1: DAG  75%
2018.10.01:11:47:23.292: GPU1 GPU1: DAG  91%
2018.10.01:11:47:23.971: GPU1 GPU1: DAG generated in 10.9 s (251.9 MB/s)
2018.10.01:11:47:23.990: GPU3 GPU3: Starting up... (0)
2018.10.01:11:47:24.265: GPU3 GPU3: Allocating DAG (2.69) GB; good for epoch upto #216
2018.10.01:11:47:24.272: GPU3 GPU3: Allocating light cache buffer (43.0) MB; good for epoch up to #216
2018.10.01:11:47:24.380: GPU3 GPU3: Generating DAG for epoch #214
2018.10.01:11:47:26.136: GPU3 GPU3: DAG  12%
2018.10.01:11:47:26.586: main Eth speed: 22.695 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:26.586: main GPUs: 1: 22.695 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:26.815: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.10.01:11:47:26.815: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x15a4af6","0xc71f2070019ebbd504621e5376431588d27f7a8fc18a5d8727e312ed60cafe38"]}

2018.10.01:11:47:26.896: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x31297a68fdcaa83fc1d28ebe2d1b120f8c2d105a90a6e1bce93272843c6439cf","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622ee9"]}
2018.10.01:11:47:27.356: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa0d0ce750a44debd162596971cea97719a7724d095868d2abd88e01eb8178e07","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622eea"]}
2018.10.01:11:47:27.356: eths Eth: New job #a0d0ce75 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:27.626: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xe7dc4396539cc79dbadde8d85852fa7cc54b39cae16ea1c22d76a0549b6036ad","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622eea"]}
2018.10.01:11:47:27.626: eths Eth: New job #e7dc4396 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:27.882: GPU3 GPU3: DAG  28%
2018.10.01:11:47:29.628: GPU3 GPU3: DAG  44%
2018.10.01:11:47:31.376: GPU3 GPU3: DAG  59%
2018.10.01:11:47:31.597: main Eth speed: 22.700 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:31.597: main GPUs: 1: 22.700 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:33.123: GPU3 GPU3: DAG  75%
2018.10.01:11:47:34.604: main GPU1: 51C 61%, GPU2: 46C 2%, GPU3: 49C 60%, GPU4:48C 6%, GPU5: 38C 58%, GPU6: 50C 11%, GPU7: 41C 60%, GPU8: 51C 17%
2018.10.01:11:47:34.872: GPU3 GPU3: DAG  91%
2018.10.01:11:47:35.570: GPU3 GPU3: DAG generated in 11.2 s (244.5 MB/s)
2018.10.01:11:47:35.592: GPU8 GPU8: Starting up... (0)
2018.10.01:11:47:35.867: GPU8 GPU8: Allocating DAG (2.69) GB; good for epoch upto #216
2018.10.01:11:47:35.875: GPU8 GPU8: Allocating light cache buffer (43.0) MB; good for epoch up to #216
2018.10.01:11:47:35.984: GPU8 GPU8: Generating DAG for epoch #214
2018.10.01:11:47:36.608: main Eth speed: 22.700 MH/s, shares: 0/0/0, time: 0:00
2018.10.01:11:47:36.608: main GPUs: 1: 22.700 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0)
2018.10.01:11:47:36.815: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.10.01:11:47:36.896: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.10.01:11:47:36.897: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xe7dc4396539cc79dbadde8d85852fa7cc54b39cae16ea1c22d76a0549b6036ad","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622eea"]}
2018.10.01:11:47:37.652: GPU8 GPU8: DAG  12%
2018.10.01:11:47:39.310: GPU8 GPU8: DAG  28%
2018.10.01:11:47:39.936: GPU3 Eth: GPU3: ETH share found!
2018.10.01:11:47:39.936: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x4f9700d0dd295c2e","0xe7dc4396539cc79dbadde8d85852fa7cc54b39cae16ea1c22d76a0549b6036ad","0x72d627580ae927e3bbde0b95dd79729b3270b25885f3a32aba404913976eca9c"]}

2018.10.01:11:47:39.936: eths Eth: Share actual difficulty: 59.9 GH (!)
2018.10.01:11:47:40.017: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
2018.10.01:11:47:40.017: eths Eth: Share accepted in 81 ms
2018.10.01:11:47:40.973: GPU8 GPU8: DAG  44%
2018.10.01:11:47:41.526: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xc1741e5030f18dfb4e219fc153427bb6244d49222faff9cd6922f0f3ee4c6eae","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622eeb"]}
2018.10.01:11:47:41.526: eths Eth: New job #c1741e50 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:41.619: main Eth speed: 43.967 MH/s, shares: 1/0/0, time: 0:00
2018.10.01:11:47:41.619: main GPUs: 1: 22.701 MH/s (0) 2: 0.000 MH/s (0) 3: 21.267 MH/s (1) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s(0) 8: 0.000 MH/s (0)
2018.10.01:11:47:41.801: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x0c933073fdb417fc9cd4e9e247be9d45d9311f2fdb888631288726471eb350cc","0x185bb34ccb2fa3c9cf41cb20429e92c96102573d3c8ed27d820dba10b5e2b962","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x622eec"]}
2018.10.01:11:47:41.801: eths Eth: New job #0c933073 from ssl://us2.ethermine.org:5555; diff: 4000MH
2018.10.01:11:47:42.632: GPU8 GPU8: DAG  59%
2018.10.01:11:47:44.295: GPU8 GPU8: DAG  75%

As you can see, it takes about 40 seconds to initialize the first 3 cards, the log is pretty much the same through the rest of the DAG creation.  It was able to get a valid share while the DAG was being created for the other cards so it's working as soon as the card is finished initializing.

on -gser 1 it would just list the first 3 cards:

GPU1 GPU1: Starting up... (0)
GPU2 GPU2: Starting up... (0)
GPU3 GPU3: Starting up... (0)

but it would never show "GPU1 Eth: Generating light cache for epoch #214" for any cards after that.

[agismaniax]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

[darkneorus]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

any reason for this, are you afraid of noise?

[agismaniax]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

any reason for this, are you afraid of noise?

i'm afraid of heat 

[crypper]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

[miner95]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

You can set custom fan setting directly in your GPU's BIOS with "SRBPolaris BIOS Editor" and all GPU's fans will be controlled with only AMD Radeon Driver.
Download it here: https://bitcointalk.org/index.php?topic=1882656.0

I use this options in "Fan" tab and my GPU's temp always is in a static temp based on my room's temp.
Minimum: 57C temp with 45% fan speed and Maximum: 65C temp with 53% fan speed but you can change it as you want.
Max temperature: 70C
Med temperature: 50C
Min temperature: 40C
Max PWM: 100%
Med PWM: 50%
Min PWM: 20%
High temperature: 60C
High PWM: 60%
Target temperature: 58C
https://cdn1.imggmi.com/uploads/2018/10/3/caf7c86db80e31eaf0ba9b17e639c041-full.png

Or you can use AMD WattMan in Radeon Settings => Global and change all of this options in there but every time you use DDU to uninstall old drivers and install new one all of your settings in WattMan will back to default options in GPU's BIOS.
So I think its better to change this options directly in GPU's BIOS that you can always just start miner without any other third-party softwares.
I use this method for my only 2x Sapphire RX 580 Nitro+ rig and it works great.

[gsrcrxsi314]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

[darkneorus]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

any reason for this, are you afraid of noise?

i'm afraid of heat 

I mean, why don't you set the fan speed to fixed 90/100%?
it won't hurt anything and surely will help to cool memory and VRM chips.

[PontusLSE]

I am trying out this miner with good results so far.

I do however have one problem that I cannot seem to resolve. No matter how many pools I enter into epools.txt the miner ALWAYS reports that I have one more pool then I have actually entered. If I only have a single line in epools.txt the miner reports two pools when it starts, it tries to connect to the first one and fails because it simply does not exist ("could not resolve host"). After some time it tries the second pool (witch in fact is the first and only one) and it starts mining.


This example is working perfectly fine with claymore, but not with phoenix.

Code:

POOL: daggerhashimoto.eu.nicehash.com:3353, WALLET: <mywallet.workename>, PSW: x, ESM: 3, ALLPOOLS: 1

I have the same problem on quite a few rigs. They are all running HiveOS (latest version).

Any suggested solutions?

Am I the only one with this problem? Any response from the dev would be appreciated.

[crypper]

i'm afraid of heat 

I mean, why don't you set the fan speed to fixed 90/100%?
it won't hurt anything and surely will help to cool memory and VRM chips.

surely it will hurt fans' bearings

[j2james]

Hi PM developers.

Today I have updated PM from 3.0c to 3.5d. And I cannot connect to CDM remote monitoring. I did not change -cdmport and -cdmpass.

I use command line parameters (not config file): -cdm 2 -cdmport 3333 -cdmpass xxxxx

Any ideas?

I have checked with config file. The same problem.

After back to 3.0c all works (with command line parameters and with config file)

[happyleper]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

With a properly configured batch file that runs at startup, yes, it can.

[gsrcrxsi314]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

With a properly configured batch file that runs at startup, yes, it can.

So natively, it cant. Thanks.

[lemonyo30]

I need Help please, im getting this error below, changed as well 5555 still the same error

No CUDA driver found
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
Listening for CDM remote manager at port 3333 in full mode
Eth: the pool list contains 4 pools
Eth: primary pool: eu1.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: QtMiner)
GPU1: 24C 70%, GPU2: 21C 70%
Eth: Could not connect to ethash pool eu1.ethermine.org:4444: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Eth: Reconnecting in 20 seconds...

[styleshifter]

Hey phoenix miner developers.
You should contact all pools like ethermine… because they need to update their websites that Phoenix Miner for Linux is now available!

[happyleper]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

With a properly configured batch file that runs at startup, yes, it can.

So natively, it cant. Thanks.

With a power reduction on a 9 GPU rig of nearly 20 percent using NVIDIA Inspector over Afterburner, I think running a batch file at startup is a small price to pay.

https://www.reddit.com/r/EtherMining/comments/9ah7qc/how_to_tune_nvidia_gpu_for_best_efficiency_nvidia/

[gsrcrxsi314]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

With a properly configured batch file that runs at startup, yes, it can.

So natively, it cant. Thanks.

With a power reduction on a 9 GPU rig of nearly 20 percent using NVIDIA Inspector over Afterburner, I think running a batch file at startup is a small price to pay.

https://www.reddit.com/r/EtherMining/comments/9ah7qc/how_to_tune_nvidia_gpu_for_best_efficiency_nvidia/

sounds like he didnt know how to use AB to its potential. if you leave the power limit high, and dont play with the clocks, then of course it'll have worse power consumption.

all you have to do is drag the power limit lower and BOOM, lower power draw. its not complicated. he had it at 70, but more or less replicated a lower power limit with a more complicated process using nv inspector.

personally i run mine at 65, and actually increase the core clock to keep hashrates the same. power cannot exceed the limit, so it forces lower voltage, essentially the same thing he did, just using a different tool.

theres nothing wrong with AB. you can achieve the same results with both. you just have to know how to use it properly.

[PhoenixMiner]

I am trying out this miner with good results so far.

I do however have one problem that I cannot seem to resolve. No matter how many pools I enter into epools.txt the miner ALWAYS reports that I have one more pool then I have actually entered. If I only have a single line in epools.txt the miner reports two pools when it starts, it tries to connect to the first one and fails because it simply does not exist ("could not resolve host"). After some time it tries the second pool (witch in fact is the first and only one) and it starts mining.


This example is working perfectly fine with claymore, but not with phoenix.

Code:

POOL: daggerhashimoto.eu.nicehash.com:3353, WALLET: <mywallet.workename>, PSW: x, ESM: 3, ALLPOOLS: 1

I have the same problem on quite a few rigs. They are all running HiveOS (latest version).

Any suggested solutions?

  Please note that the first one or two pools from the pool list may come from the command line. If you have specified one of the options -pool, -wal, -pass, -coin, or -proto on the command line (perhaps via the custom miner settings of the HiveOS control panel), this will specify a pool and since it is the first pool in the list, PhoenixMiner will first try to connect to it. You just need to remove all these options from the command line and then only the pools in epools.txt will matter.

Code:

...

As you can see, it takes about 40 seconds to initialize the first 3 cards, the log is pretty much the same through the rest of the DAG creation.  It was able to get a valid share while the DAG was being created for the other cards so it's working as soon as the card is finished initializing.

on -gser 1 it would just list the first 3 cards:

GPU1 GPU1: Starting up... (0)
GPU2 GPU2: Starting up... (0)
GPU3 GPU3: Starting up... (0)

but it would never show "GPU1 Eth: Generating light cache for epoch #214" for any cards after that.

   Thank you for the log! Apparently, the light cache generation is not causing the problem but perhaps some incompatibility of the Linux kernels with some Nvidia cards (the light cache is created only once by whatever GPU starts first and then is used by all the other GPUs). We have included same measures in the development version of 3.6 to detect better what happens right after the light cache generation, and we will update the CUDA kernels for Linux, so hopefully this will solve the problem in the next version.

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

   No, with PhoenixMiner you can either fix the temperature (e.g. -tt 60) or the fan speed (with negative number after -tt). You can also set a maximum fan speed but that's it. We will update the hardware control options in Mil Shield 3.6 but such custom fan curves are beyond what we have at mind for now.
 

Hi PM developers.

Today I have updated PM from 3.0c to 3.5d. And I cannot connect to CDM remote monitoring. I did not change -cdmport and -cdmpass.

I use command line parameters (not config file): -cdm 2 -cdmport 3333 -cdmpass xxxxx

Any ideas?

I have checked with config file. The same problem.

After back to 3.0c all works (with command line parameters and with config file)

   The only change with respect to remote monitoring in 3.5d is that now it starts 10-20 seconds after the miner starts but otherwise it should be working fine - we are using it 24/7 on our test rigs without any problems. From our own experience, this problem is perhaps related to Windows Firewall, which blocks the CDM port for the executable of the new version (it should show you a pop-up window, asking if you want to open the port the first time you start the a new version of PhoenixMiner). Another possible reason (again related to Windows Firewall) is that it may "decide" that the local network is "public" instead of "private" and it has much more strict rules for public networks, so it again blocks the CDM port of PhoenixMiner. A quick test to see if the Firewall is the culprit is to turn it off for a short time and see if the remote management works.

I need Help please, im getting this error below, changed as well 5555 still the same error

Code:

No CUDA driver found
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
Listening for CDM remote manager at port 3333 in full mode
Eth: the pool list contains 4 pools
Eth: primary pool: eu1.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: QtMiner)
GPU1: 24C 70%, GPU2: 21C 70%
Eth: Could not connect to ethash pool eu1.ethermine.org:4444: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Eth: Reconnecting in 20 seconds...

   There are two possible reasons for this: you either have connection problems -  check your network settings, DNS settings, etc., or you have left YourWallet as the wallet name in the command-line settings (the .bat file), or in the epools.txt file - in such case replace YourWallet with your actual wallet address.

[btckesh]

phoenixminer for linux, nice guys. this is what i've been waiting for and now i've almost overseen it! any differences compared to windows with 1070ti/1080 cards?

[Matkurb]

I always use custom fan curve setting in MSI Afterburner or Sapphire Trixx. I set the fan speed to 5 points above the GPU's temperature. For example, if the GPU's temp is 52C, then the fan will spin at speed of 57%, 65C temp 70% fan, and it always spin based on current GPU's temp. Can this custom fan curve setting be done via PhoenixMiner?

ALWAYS use 3rd party soft to control clocks, power and fans: OverdriveNtool for red and nvidiaInspector for green; don't use AB - it's shit. Don't use miners for controls.

AB works just fine. And will apply clocks at boot. Can nvidia inspector do that?

With a properly configured batch file that runs at startup, yes, it can.

So natively, it cant. Thanks.

With a power reduction on a 9 GPU rig of nearly 20 percent using NVIDIA Inspector over Afterburner, I think running a batch file at startup is a small price to pay.

https://www.reddit.com/r/EtherMining/comments/9ah7qc/how_to_tune_nvidia_gpu_for_best_efficiency_nvidia/

That is great. I will give it a try.