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

[Branko]

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

Never use GPU-Z for power measurements, hardware watt meter is the only sure way. Everything else is just software estimate
that is often pretty wrong

Theyre not expensive, either:

https://www.ebay.com/itm/AC-power-meter-220v-digital-wattmeter-energy-monitor-electricity-consumption-KI/153101520651?hash=item23a58fcf0b:m:mAjCDfztrd1tW9iDnDvS1xw

[1714210363]

1714210363

[1714210363]

1714210363

[1714210363]

1714210363

[1714210363]

1714210363

[1714210363]

1714210363

[1714210363]

1714210363

[simcity4]

miner freeze
here log

1970.01.01:03:45:10.965: unkn OpenCL driver version: 17.31.0
2018.09.10:10:42:07.996: main Phoenix Miner 3.5b Windows/msvc - Release build
2018.09.10:10:42:07.996: main Cmd line: -amd -coin clo -pool stratum+tcp://moac.bylt.gq:5005 -wal mywallet -worker amd -pass x -log 1 -tstop 70 -cdm 0 -retrydelay 0 -cclock 965 -mclock 1875 -powlim 0 -cvddc 850 -mvddc 900
2018.09.10:10:42:07.996: main Available GPUs for mining:
2018.09.10:10:42:07.996: main GPU1: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.09.10:10:42:08.025: main ADL library initialized

[Digital_Seytan]

miner freeze v3.5b detects all devices but then ends with error !!!!

Code:

Phoenix Miner 3.5b Windows/msvc - Release build
-----------------------------------------------

Available GPUs for mining:
GPU1: GeForce GTX 1060 (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU2: GeForce GTX 1060 (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU3: GeForce GTX 1060 (pcie 3), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU4: GeForce GTX 1060 (pcie 4), CUDA cap. 6.1, 6 GB VRAM, 10 CUs

please HELP

[53nsk]

Tried 3.5b on 2 more amd rigs - same issue. Drivers are 18.5.1 and 18.5.2.

[Risecrypto]

Decided to try Phoenix Miner after Claymore kept giving DAG errors last few days and shutting the Mining Rig off.

Running 10 GPU RX580
roughly Hashrate is 1.5 Mh/s more on each card then Claymore miner.

seems to run a little more stable, and Dag file are currently not causing Dag error after 12hrs mining.
(Claymore gave Dag errors)

Will keep monitoring and update you guys.

[laik2]

BUG report: Linux version PM 3.5a has support for fan/temp only upto 7 devices.
http://prntscr.com/kspvgc
Temperature monitoring will not work on 7+ devices, otherwise it seems the fastest and most efficient ethash miner to me. Good job!
EDIT: Does rmode on linux execs reboot.bat or reboot.bash/sh ?
EDIT2: It does read temp/fan till PCI 0x09, miner marks it as 0x10 but its actually 0x0a.

[ZoomhashLLC]

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

Never use GPU-Z for power measurements, hardware watt meter is the only sure way. Everything else is just software estimate
that is often pretty wrong

Theyre not expensive, either:

https://www.ebay.com/itm/AC-power-meter-220v-digital-wattmeter-energy-monitor-electricity-consumption-KI/153101520651?hash=item23a58fcf0b:m:mAjCDfztrd1tW9iDnDvS1xw

We have found even some plug-in watt meters are not accurate and can easily become uncalibrated.

Depending on your voltage you can find a cheap metered PDU that will tell you your amperage draw for under $150.

[Soliqesh]

green kernel 1275w 304mh/s, without 308mh/s 1287w on wattmeter. 

[salvo2002]

Hi all, just reporting my results... on:

PhoenixMiner 3.5a -- First release with support for Linux

Code:

4.10.17-hiveos #1 SMP Sun Dec 10 08:48:43 EET 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Based on this post over at HiveOS community: https://forum.hiveos.farm/t/custom-miner-integration/4521/212

2-3 MH/s increase (reported hashrate) over Claymore 11.9, BUT a significant increase in stale shares! [using https://www.hiveon.net/ ETH pool]

screenshot:
https://ibb.co/fBu5h9

[PhoenixMiner]

3.5b same result, log:

1970.01.01:07:15:48.496: unkn OpenCL driver version: 18.5.1
...

I tried the 3.5b. No change:

Code:

...

miner freeze
here log
...

   Thank you for reporting this problem. We have send a PM to each of you with additional information and questions that will help us resolve it.

-clgreen 1   what is this parameter

   Activates new power-efficient kernels for AMD RX460/470/480/560/570/580. They aren't faster than the normal kernels (in most cases are slightly slower but not always) but should lower your power consumption by 2-3 W per card (RX570). Whether they are more optimal for you depends on the price of electricity and the settings of your cards. Please note that you have to run auto-tune again to find the optimal GT settings for these kernels as they are different from the normal kernels.

   Good news! Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.

Did you see: https://bitcointalk.org/index.php?topic=2647654.msg43145022#msg43145022

   Yes, thank you for this suggestion. We are planning much more feature-rich remote management API in the future releases (we will keep compatibility with Claymore's as fallback). Note that you can get the per-GPU hashrate with the current API. The Nvidia overclocking options are planned for the next release.

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

   You should see about 2-3W per card but probably not with GPU-Z. We have measured 2.4W per RX570 with settings 1100/2000  MHz and 870mV core voltage. The hashrate drop was from 29.15 to 29.0 MH/s.

green kernel 1275w 304mh/s, without 308mh/s 1287w on wattmeter. 

   Please make sure that you have auto-tuned the green kernels (the old GT values are not optimal for the green kernels). Sometimes it may take same time before you see the real difference in power (30 mintues or so after starting). Also the drops in the power and in the hashrate depend on the settings of the card and the ratio between the core clock and memory clocks, as well as the memory timings. The green kernels can be used only on some gpus by specifying -clgrean for each gpu individually: for example -clgreen 1,1,0,0,0 will run the green kernels only on the first two GPUs in five GPU rig.

miner freeze v3.5b detects all devices but then ends with error !!!!

Code:

....

please HELP

   Can you tell us if you see any error message window, or the miner just freezes without showing anything?

Здpaвcтвyйтe кoллeги мaйнepы!
cтoлкнyлcя c пpoблeмoй пpи нacтpoйкe мaйнepa PhoenixMiner , в OS HiveOS
Hacтpaивaл coглacнo oпиcaния в пocтy: https://forum.hiveos.farm/t/custom-miner-integration/4521/212?u=chivekubik
нacтpoить yдaлocь, нo пocлe зaпycкa мaйнepa, cмoтpю в лoги и вижy:

Eth: New job #2699da4d from eu1-etc.ethermine.org:4444; diff: 4000MH
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth: New job #8e242334 from eu1-etc.ethermine.org:4444; diff: 4000MH

xeшpeйт нe пoднимaeтcя в тeчeниe 15 мин.
Teмпepaтypa GPU нe пoднимaeтcя
________
Moe жeлeзo:
OS:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=“Ubuntu 16.04.4 LTS”
__
GPU:
GeForce GTX 1080 8119 MiB · MSI - 3 шт.
____
Пpилaгaю cкpиншoты c нacтpoйкaми https://prnt.sc/ksozce
и xeшpeйтoм https://prnt.sc/ksozsi
Фepмa https://prnt.sc/kspa8p
_______________
Пoмoгитe пoжaлyйcтa, нacтpoить кoppeктнo мaйнep

   Can you please send us (or post here) the first few pages from the log file? It seems that the DAG generation never finishes but we can't be sure because we can see the start of the log in your screenshot, and then an excerpt after a few minutes but not what happens in between.

BUG report: Linux version PM 3.5a has support for fan/temp only upto 7 devices.
http://prntscr.com/kspvgc
Temperature monitoring will not work on 7+ devices, otherwise it seems the fastest and most efficient ethash miner to me. Good job!
EDIT: Does rmode on linux execs reboot.bat or reboot.bash/sh ?
EDIT2: It does read temp/fan till PCI 0x09, miner marks it as 0x10 but its actually 0x0a.

   Thank you for reporting this problem. We haven't tested the Linux version on a rig with more than 6 GPUs yet and sure enough, there is a problem. We have found the issue and it will be fixed in 3.5b, which will be released later today or first thing tomorrow after we are sure that there aren't any more problems that we can find here.

Hi all, just reporting my results... on:

PhoenixMiner 3.5a -- First release with support for Linux

Code:

4.10.17-hiveos #1 SMP Sun Dec 10 08:48:43 EET 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Based on this post over at HiveOS community: https://forum.hiveos.farm/t/custom-miner-integration/4521/212

2-3 MH/s increase (reported hashrate) over Claymore 11.9, BUT a significant increase in stale shares! [using https://www.hiveon.net/ ETH pool]

screenshot:

   Thank you, this is very helpful. Most probably the miner can't recognize the OpenCL driver and some of the most aggressive driver-specific optimizations aren't used. Can you please check if you have a line like this:

Code:

2018.09.10:06:24:11.757: main OpenCL driver version: 17.40

in the start of PhoenixMiner log (it should be among the first five to ten lines in the log file)? Also, could you please tell us the version of your AMD drivers?

[bitcoin.dbi]

  Activates new power-efficient kernels for AMD RX460/470/480/560/570/580. They aren't faster than the normal kernels (in most cases are slightly slower but not always) but should lower your power consumption by 2-3 W per card (RX570). Whether they are more optimal for you depends on the price of electricity and the settings of your cards. Please note that you have to run auto-tune again to find the optimal GT settings for these kernels as they are different from the normal kernels.

Do i need to kick out -gt 11 command from bat file if i want to use this new green kernel?

The green kernels can be used only on some gpus by specifying -clgrean for each gpu individually: for example -clgreen 1,1,0,0,0 will run the green kernels only on the first two GPUs in five GPU rig.

If i got rig with 5 cards (1-4 AMD and 5  Nvidia) what should i write in bat file? -clgreen 1,1,1,1,0 or -clgreen 1,1,1,1
Thanks.

-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)

Is it possible to add rmode which will reboot PC instead of miner (want to use wdog if one cart will stuck)? Or maybe i can just put "shutdown /r /o /t 0" in reboot.bat file?

[ZoomhashLLC]

Very excited to see the Linux version in fruition PhoenixMiner, great job!

We may look into this version after the beta for our customers depending on the stability.

[Bigdrago]

With green kernels enabled (13 amd 570):
Went from 1624W 406 mh/s to 1590W 407.5 mh/s
Thanks

[thepeppi]

thnx m8

3.0 was bad my share rate dropped under 0.35 per card per minute (rx amd cards) should be a minimum of 0.42

things are important for me and i think for every miner

• share rate
• stabilaty
• low devfee

if you can make this then i am shure you will gain many many users
its not for nothing that clayM has NoFee hacks he is taking way to much fee from us

30 minutes mining and still a low share rate 0.37 per minute per card
no good sorry


pool ethermine

[salvo2002]

   Thank you, this is very helpful. Most probably the miner can't recognize the OpenCL driver and some of the most aggressive driver-specific optimizations aren't used. Can you please check if you have a line like this:

Code:

2018.09.10:06:24:11.757: main OpenCL driver version: 17.40

in the start of PhoenixMiner log (it should be among the first five to ten lines in the log file)? Also, could you please tell us the version of your AMD drivers?

AMD driver version: 17.50-511655

Code:

dpkg -l amdgpu-pro
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                                  Version                         Architecture                    Description
+++-=====================================================-===============================-===============================-===============================================================================================================
ii  amdgpu-pro                                            17.50-511655                    amd64                           Meta package to install amdgpu Pro components.

I don't see a

Code:

"Main OpenCL driver version: ..."

Here are the first 100 lines of the log file... closest thing to any "OpenCL" statements are

Code:

Using new optimized OpenCL kernels (device name 'Ellesmere')
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 32 CUs

I shortened the "jsonrpc":"2.0","result" strings...

Code:

2018.09.11:18:59:32.140: main Phoenix Miner 3.5a Linux/gcc - Release build
2018.09.11:18:59:32.140: main Cmd line:
2018.09.11:18:59:32.140: main config.txt: -mport -3333 -r 1 -logfile lastrun_noappend.log -logdir /var/log/miner/custom/ -tt 0
2018.09.11:18:59:32.145: main Unable to enum CUDA GPUs: unknown error
2018.09.11:18:59:32.182: main Available GPUs for mining:
2018.09.11:18:59:32.182: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU2: Radeon RX 580 Series (pcie 2), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU4: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU7: Radeon RX 570 Series (pcie 8), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU8: Radeon RX 580 Series (pcie 9), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU9: Radeon RX 580 Series (pcie 10), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.183: main AMD sysfs monitor initialized
2018.09.11:18:59:32.184: main Eth: the pool list contains 4 pools
2018.09.11:18:59:32.184: main Eth: primary pool: naw-eth.hiveon.net:4444
2018.09.11:18:59:32.184: main Starting GPU mining
2018.09.11:18:59:32.184: wdog Starting watchdog thread
2018.09.11:18:59:32.184: main Eth: Connecting to ethash pool naw-eth.hiveon.net:4444 (proto: EthProxy)
2018.09.11:18:59:32.236: eths Eth: Connected to ethash pool naw-eth.hiveon.net:4444 (54.183.35.85)
2018.09.11:18:59:32.236: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["xxxxxxx","x"]}
2018.09.11:18:59:32.264: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":1}
2018.09.11:18:59:32.265: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.09.11:18:59:32.292: eths Eth: Received: {"jsonrpc":"2.0","result":["x","x","x"],"id":5}
2018.09.11:18:59:32.292: eths Eth: New job #694418d0 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:32.292: GPU1 GPU1: Starting up... (0)
2018.09.11:18:59:32.292: GPU1 Eth: Generating light cache for epoch #210
2018.09.11:18:59:32.304: GPU2 GPU2: Starting up... (0)
2018.09.11:18:59:32.304: GPU3 GPU3: Starting up... (0)
2018.09.11:18:59:32.304: GPU4 GPU4: Starting up... (0)
2018.09.11:18:59:32.304: GPU5 GPU5: Starting up... (0)
2018.09.11:18:59:32.304: GPU6 GPU6: Starting up... (0)
2018.09.11:18:59:32.304: GPU7 GPU7: Starting up... (0)
2018.09.11:18:59:32.304: GPU8 GPU8: Starting up... (0)
2018.09.11:18:59:32.304: GPU9 GPU9: Starting up... (0)
2018.09.11:18:59:32.399: main Listening for CDM remote manager at port 3333 in read-only mode
2018.09.11:18:59:34.116: eths Eth: Received: { "jsonrpc":"2.0", "result": ["x","x","x"] }
2018.09.11:18:59:34.116: eths Eth: New job #eb3d7c98 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:34.296: GPU1 GPU1: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.296: GPU1 GPU1: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.296: GPU1 GPU1: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.391: GPU2 GPU2: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.391: GPU2 GPU2: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.391: GPU2 GPU2: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.403: GPU1 GPU1: Generating DAG for epoch #210
2018.09.11:18:59:34.487: GPU3 GPU3: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.487: GPU3 GPU3: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.487: GPU3 GPU3: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.498: GPU2 GPU2: Generating DAG for epoch #210
2018.09.11:18:59:34.582: GPU4 GPU4: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.582: GPU4 GPU4: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.582: GPU4 GPU4: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.595: GPU3 GPU3: Generating DAG for epoch #210
2018.09.11:18:59:34.677: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.678: GPU5 GPU5: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.678: GPU5 GPU5: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.690: GPU4 GPU4: Generating DAG for epoch #210
2018.09.11:18:59:34.773: GPU6 GPU6: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.773: GPU6 GPU6: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.773: GPU6 GPU6: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.785: GPU5 GPU5: Generating DAG for epoch #210
2018.09.11:18:59:34.868: GPU7 GPU7: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.868: GPU7 GPU7: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.868: GPU7 GPU7: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.881: GPU6 GPU6: Generating DAG for epoch #210
2018.09.11:18:59:34.964: GPU8 GPU8: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.964: GPU8 GPU8: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.964: GPU8 GPU8: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.977: GPU7 GPU7: Generating DAG for epoch #210
2018.09.11:18:59:35.060: GPU9 GPU9: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:35.060: GPU9 GPU9: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:35.060: GPU9 GPU9: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:35.072: GPU8 GPU8: Generating DAG for epoch #210
2018.09.11:18:59:35.167: GPU9 GPU9: Generating DAG for epoch #210
2018.09.11:18:59:36.162: GPU1 GPU1: DAG  31%
2018.09.11:18:59:36.181: GPU2 GPU2: DAG  38%
2018.09.11:18:59:36.410: GPU3 GPU3: DAG  31%
2018.09.11:18:59:36.502: GPU4 GPU4: DAG  31%
2018.09.11:18:59:36.600: GPU5 GPU5: DAG  31%
2018.09.11:18:59:36.696: GPU6 GPU6: DAG  31%
2018.09.11:18:59:36.755: GPU8 GPU8: DAG  38%
2018.09.11:18:59:36.791: GPU7 GPU7: DAG  31%
2018.09.11:18:59:36.851: GPU9 GPU9: DAG  38%
2018.09.11:18:59:36.860: eths Eth: Received: { "jsonrpc":"2.0", "result": ["x","x","x"] }
2018.09.11:18:59:36.860: eths Eth: New job #d5e03598 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:37.205: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.09.11:18:59:37.205: 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) 9: 0.000 MH/s (0)
2018.09.11:18:59:37.796: GPU2 GPU2: DAG  75%
2018.09.11:18:59:37.912: GPU1 GPU1: DAG  63%
2018.09.11:18:59:38.158: GPU3 GPU3: DAG  63%
2018.09.11:18:59:38.248: GPU4 GPU4: DAG  63%
2018.09.11:18:59:38.348: GPU5 GPU5: DAG  63%
2018.09.11:18:59:38.369: GPU8 GPU8: DAG  75%
2018.09.11:18:59:38.444: GPU6 GPU6: DAG  63%
2018.09.11:18:59:38.464: GPU9 GPU9: DAG  75%

[PhoenixMiner]

Do i need to kick out -gt 11 command from bat file if i want to use this new green kernel?

   Yes, at least the first time, because auto-tune won't run if explicit GT value(s) are specified in the command line, or in the config.txt file. After that you can write down or copy the GT values shown when you press s in the console (or check the logs via remote management), and add these GT values in your bat file or config.txt.

If i got rig with 5 cards (1-4 AMD and 5  Nvidia) what should i write in bat file? -clgreen 1,1,1,1,0 or -clgreen 1,1,1,1
Thanks.

  If you want to run the green kernels on all AMD cards, there is no need to specify multiple values, -clgreen 1 is enough. You need multiple -clgreen values only if you want to run the green kernels only on some AMD cards, while running the normal kernels on others.
   

Is it possible to add rmode which will reboot PC instead of miner (want to use wdog if one cart will stuck)? Or maybe i can just put "shutdown /r /o /t 0" in reboot.bat file?

   Yes, you have to put the corresponding command in reboot.bat (or reboot.sh on Linux).

Very excited to see the Linux version in fruition PhoenixMiner, great job!

We may look into this version after the beta for our customers depending on the stability.

    Great!  Let us know if you have any questions.

With green kernels enabled (13 amd 570):
Went from 1624W 406 mh/s to 1590W 407.5 mh/s
Thanks

   Nice, this is in line with our results. Still, YMMV as always.

   Thank you, this is very helpful. Most probably the miner can't recognize the OpenCL driver and some of the most aggressive driver-specific optimizations aren't used. Can you please check if you have a line like this:

Code:

2018.09.10:06:24:11.757: main OpenCL driver version: 17.40

in the start of PhoenixMiner log (it should be among the first five to ten lines in the log file)? Also, could you please tell us the version of your AMD drivers?

AMD driver version: 17.50-511655

   Thank you! We have tracked down this driver, and tuned the optimizations to work with it. It should work as intended in PhoenixMiner 3.5c, which will be released in a few minutes.

[PhoenixMiner]

There is a new version for Windows and LInux: PhoenixMiner 3.5c, which can be downloaded from here:

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

    File: PhoenixMiner_3.5c_Windows.zip
    ===================================
   SHA-1: 8b3e25069cd73a9601940748a5044d6eca6e2b96
 SHA-256: e831c6f525b578ff52f8bfc07522b15da14ac06ff93952f231a3d9eac3eeb92e
 SHA-512: ec43b7c6350732b0af7b2f73b4d12117fda1a41572e593e2db19634495cd203d28509c3c0dcf3024551a5b6ee0c9f8cfe079333381c225edfeee7c5f2cdb1d70


    File: PhoenixMiner_3.5c_Linux.tar.gz
    ====================================
   SHA-1: 507c0a69d734519e74e11c89a457d69ce2445106
 SHA-256: 72b4b78fc09770c43a6869923d6bb729571e20aa81da1ccaf8f21392e2d5a7db
 SHA-512: 60505a339be0828f436354906b38bb42ab8c958f2070ef42058015409e5774eb4c4f914b722e055f0c443fd18138e370ddaf277b69ac6a0e07e74569fa7656aa

Version 3.5c fixes the problems that were discovered during the beta-testing of 3.5a and 3.5b, including the following:
  * Fixed freezing problems immediately after GPU are recognized
  * Fixed hardware monitoring problem under Linux with more than 6 GPUs
  * Fixed problems under Linux with unrecognized drivers and stale share increases

Some useful notes related to the new features:

• The new -clgreen kernels have completely different optimal GT values, so you have to run auto-tune again to get the optimal hashrate with them
• Unfortunately, the time wasn't enough to implement HW control in Linux, so only the monitoring works there (i.e. showing fan speeds and temperatures but not controlling them). This will be implemented in the next release.

Finally, here are the changes since the 3.0c again:

* Support for Linux (tested on Ubuntu 16.04 LTS and Debian 9.5 stable). Note that we have tested with AMD GPU-Pro drivers (not the open source drivers) and the official Nvidia closed-source drivers. Please note that this is the first version that supports Linux, so some glitches are to be expected. Do not hesitate to write us about any problems.
* With the recent drop in prices of most cryptos, we are trying to come up with ways to increase the profitability. Since the cost of the electric power a major factor now, we worked hard to create new, power-efficient kernels for most widely used AMD cards (RX580/570/560/480/470/460). To use these kernels, you must specify the option -clgreen 1 on the command-line, or in the config.txt file. In our tests the green kernels lower the power consumption by 2-3% on the supported cards. These kernels may also slightly lower the hashrate (by 0.2-0.5%), so you have to check if they are more efficient for you depending on the electricity costs in your area.
* Small improvements in the normal AMD kernels to increase hashrate (RX4xx, RX5xx, Tonga, and Fury)
* Added advanced stats option (you have to turn this on with the command-line option -astats 1) that will try to estimate the daily earnings depending on the current price of the coin you are mining and the current difficulty. Note that this is only an estimation and it uses information from third-party web sites, which may not be accurate.
* Added support for direct mining of DubaiCoin (DBIX)
* Added -leaveoc option to prevent resetting of the HW OC settings to defaults on exit
* Many small fixes

[ganzocrypt]

Hello,

just tried the new -clgreen 1 but hashrate  went from 32 to 22 Mhs. I run Sapphire Pulse 580 8Gb bios modded on Windows 10.
Here are the options I use:

PhoenixMiner.exe -pool ssl://eu1-etc.ethermine.org:5555 -pool2 ssl://............. -wal ......................AMD -proto 3 -pass x -coin etc -cdm 0 -stales 0 -clgreen 1 -amd -acm -astats 1 -leaveoc -mi 14 -gt 30 -gser 2 -wdog 1 -tt 70 -tmax 80 -fanmin 70 -fanmax 80 -powlim -10 -cclock 1200 -mclock 2050,2250,2210,2250,2250,2250,2050 -cvddc 930,900,900,900,900,900,930 -mvddc 960,950,960,960,950,950,960 -log 0


any idea?

[bategojko74]

Remove -gt 30

[bategojko74]

Hello,

just tried the new -clgreen 1 but hashrate  went from 32 to 22 Mhs. I run Sapphire Pulse 580 8Gb bios modded on Windows 10.
Here are the options I use:

PhoenixMiner.exe -pool ssl://eu1-etc.ethermine.org:5555 -pool2 ssl://............. -wal ......................AMD -proto 3 -pass x -coin etc -cdm 0 -stales 0 -clgreen 1 -amd -acm -astats 1 -leaveoc -mi 14 -gt 30 -gser 2 -wdog 1 -tt 70 -tmax 80 -fanmin 70 -fanmax 80 -powlim -10 -cclock 1200 -mclock 2050,2250,2210,2250,2250,2250,2050 -cvddc 930,900,900,900,900,900,930 -mvddc 960,950,960,960,950,950,960 -log 0


any idea?

Remove -gt 30