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

[Soliqesh]

@Pheonixminer Pls fix -tt function, works so badly with many cards.(Asus Strix rx580 8gb, XFX rx570 8gb, Asus Strix Vega 64)

  Sorry about that, could you please tells how it behaves and how you would you like it to. From the aforementioned cards the support is probably worst for the Vega, but we will improve it in the next release.

Asus Strix Radeon RX580 8GB Gaming, this cards works incorrect with -tt parameter, if i set -tt 60, fan speed jump from 0% to 41% only, and cards are trying cool yourself to 51-54 degrees   Same situation with Vega 64 Asus Strix.
XFX Radeon RX 580 GTR 8GB, this cards are working correct with -tt 60, but if temperature increases on cards, fan speed stopped on 59% and the cards begin to raise the temperature higher the limit 60. Same situation with other XFX cards.

  If you are using Linux, this is normal, as we don't support -tt at all in this version - it will be added in the next version. However, if this is under Windows, and you are using older driver (anything older that 18.x.x), you should upgrade to 18.x.x driver because the HW control support before that is broken in the drivers.

I tested all drivers, same situation, i report this problem before and you say this(down). This screenshot https://imgur.com/a/wyRoKjE shows, -tt 60 works only with XFX cards(Red line), Asus Strix RX 580 8GB works badly(Blue line)

Hi all, have rig with x6 RX580 8GB(x3 XFX GTS and x3 STRIX TOP Gaming), when i start miner with parameter -tt 64, miner set only for 3 cards XFX (Claymore work fine for all gpu). Help pls( Screen: https://i.imgur.com/LPRmrWq.png

  Please send us the log file (the first few minutes after starting are enough). Obviously there is some problem when initializing ADL on your STRIX cards. We had similar problem with an MSI card that wouldn't accept any overclocking settings via ADL calls but we have to see to log to be sure.

Hi, when i set -tt 63 it works, but not correctly(miner set target temperature - 63C for x3 STRIX TOP RX580 8G but in the process of mining cards keep a static 41% fan speed(Screen https://i.imgur.com/dYyZza4.png), if -tt 64 it doesnt work for these cards anymore.
Logs:
1)When i set -tt 63 - https://drive.google.com/open?id=1E_Cnx0W2MQWU5qCwffkaWYK9LpTQvF2F
2)When i set -tt 64 - https://drive.google.com/open?id=1oHTf0yeRxXtfysoFEC_lrfKM22zufbBa
3)When i set -tt 63 but cards have static fan speed 41% - https://drive.google.com/open?id=1yw-5bvCOyN-Vi9ppqVkYdvFAEQ-GDaMa

  Thank you for the logs. It appears that ADL is actually working correctly even on the Strix cards. The messages for applying OC settings are missing because the cards are already at these settings (PhoenixMiner first checks if the settings are the same before applying them). We will add -resetoc option in the next version to reset all OC settings when the miner starts to start from "clean sheet" so to speak.
   However the root cause of the problem that you are experiencing seems to be that the Strix cards are reporting too high minimal FAN rpms (1722 rpm), which are probably exactly these 41% that you are seeing. We will make some changes in the next release to avoid abiding by these limits if they are too low or too high.

[1715546270]

1715546270

[1715546270]

1715546270

[1715546270]

1715546270

[1715546270]

1715546270

[agismaniax]

It seems -clkernel 1 option is not working for my rx570/580 4gb. The power consumption on-the-wall is still the same. I also didnt put -gt option in my config.txt

UPDATE:
Try -clkernel 2 and auto-tune gpu again.
And still the same hashrate and power consumption.

The option for lower power consumption is -clgreen 1
It is not clkernel -1

Sorry, my mistake. I get 2-4 watt power reduction with 2 gpu (rx570 and rx580) and no hashrate drop.

[PhoenixMiner]

We will try to source a gfx804 based RX550 to see what is going on.

I'll be glad to help. Let me know if you need more logs, test new build or something else.

   We have ordered three different RX550 from different makes, hopefully at least one will be with gfx804 One last thing, if you are testing with -clgreen 1, hashrate may be lower (in this case significantly lower apparently), so please try without -clgreen 1 and see if it makes a difference.

   The config seems OK apart from the two -mport options but the second one just overrides the value of the first one, so this isn't really a problem. As for the missing temperature and fan data - this is quite strange, we haven't seen this - perhaps this depends on how hiveOS extracts these: from the miner, or independently. It seems that hiveOS 0.5-74 is based on Ubuntu 18.04, which may be cause or at least part of the problem - we are testing now with Ubuntu 18.04 LTS, so we hope that we will find and fix any problems.

   As for the -tt not working - this is normal, as we do not support hardware control under Linux yet. It will be added in the next version.

I think it's because there is a -tt 0 in there...

   You are absolutely right!  After the initial implementation, we haven't used -tt 0 at all, but it will definitely turn off the hardware monitoring.

Can you add MOAC and CLO coins please? Thanks.

   CLO is added already (since 3.0c), you just need to specify -coin clo and it will mine the devfee in CLO. As for MOAC - it will be added in 3.5d, which will be released later today or tomorrow morning.

Good Job, developers, such a nice miner.

I'm linux user and on the way to migrate my machines on Phoenix, but some bugs don't allow me.

The fan management is just bad. The temperature is good got, but fans doesn't move their first percentage and this could take the cards to hell.

Probably know, but the fans for AMD are managed from (AMDGPU PRO):
/sys/class/drm/card*/device/hwmon/hwmon*/pwm1 (from 0 to 255)
PS: If there is internal GPU - this will confuse the next cards - they'll be +1.

But only root can change this, so

This cron work for me on Ubuntu (I think this is not working on Debian):
@reboot chown [miner_username]: /sys/class/drm/card*/device/hwmon/hwmon*/pwm1

Hope it helps for better fan management.

It's possible to write a custom script, but don't think is the right way to manage the fans.

   Thank you for trying our miner! Unfortunately, the cyrrent Linux version, there is no support for controlling the fans, voltages, etc. It definitely will be added in the next version but for 3.5 you have to use external software to control the clocks and voltages. We will also finally add Nvidia hardware control for both Windows and Linux in the next version (3.6).

I tested all drivers, same situation, i report this problem before and you say this(down). This screenshot https://imgur.com/a/wyRoKjE shows, -tt 60 works only with XFX cards(Red line), Asus Strix RX 580 8GB works badly(Blue line)

   Sorry about these problems. Unfortunately, there is no easy way to fix this as with our cards the settings work more or less OK. In the next release (3.6), we will add more ways to control the temperatures, voltages and fan speeds, which will hopefully work better for your cards than the current method via the AMD-approved ADL library API.

[bitcoin.dbi]

   CLO is added already (since 3.0c), you just need to specify -coin clo and it will mine the devfee in CLO. As for MOAC - it will be added in 3.5d, which will be released later today or tomorrow morning.

Big thanks. Because it is pretty annoying when devfee switching DAG file 2 times.
P.S. any ideas why this command doesnt work with r9 280x card or it only support Polaris? -cvddc 1050 -cclock 1130 -mclock 1374  -fanmin 100 -powlim -15

[Soliqesh]

@Pheonixminer -clgreen 1 works so good with RX 580/570 4gb memory, stable hashrate - lower power consumption , but with 8gb memory RX570/580 if i try this kernel my cards have chaotic hashrate, rig 309 mh/s with standart kernel, if -clgreen kernel 304-307, its normal? Logfile https://drive.google.com/file/d/1G4uknUONcpITDHQfBCJkrRx3HfdWaAPB/view?usp=sharing

[ATrump]

We have ordered three different RX550 from different makes, hopefully at least one will be with gfx804

Great news! I'm waiting at least 15 Mh/s

One last thing, if you are testing with -clgreen 1, hashrate may be lower (in this case significantly lower apparently), so please try without -clgreen 1 and see if it makes a difference.

All my previous tests was made without clgeen. By the way, it looks like clgreen doesn't work with gfx804 (See 2018.09.17:15:36:36.474).

Code:

2018.09.17:15:36:31.224: main Phoenix Miner 3.5c Linux/gcc - Release build
2018.09.17:15:36:31.224: main Cmd line: 
2018.09.17:15:36:31.224: main config.txt: -r 1 -logfile /var/log/miner/phoenixminer/lastrun_noappend.log -tt 68 -tstop 82 -allpools 1 -mport 3335 -gpus 4 -tt 1 -clkernel 2 -clgreen 1 
2018.09.17:15:36:31.231: main Unable to enum CUDA GPUs: unknown error
2018.09.17:15:36:31.383: main OpenCL driver version: 18.10-572953
2018.09.17:15:36:31.383: main Available GPUs for mining:
2018.09.17:15:36:31.383: main GPU1: Radeon 500 Series (pcie 10), OpenCL 1.2, 4 GB VRAM, 8 CUs
2018.09.17:15:36:31.384: main AMD sysfs monitor initialized
2018.09.17:15:36:31.385: main Eth: the pool list contains 2 pools
2018.09.17:15:36:31.385: main Eth: primary pool: eu-eth.hiveon.net:4444
2018.09.17:15:36:31.385: main Starting GPU mining
2018.09.17:15:36:31.385: main Eth: Connecting to ethash pool eu-eth.hiveon.net:4444 (proto: EthProxy)
2018.09.17:15:36:31.385: wdog Starting watchdog thread
2018.09.17:15:36:31.585: main Listening for CDM remote manager at port 3335 in full mode
2018.09.17:15:36:31.586: main GPU1: 65C 100%
2018.09.17:15:36:31.607: eths Eth: Connected to ethash pool eu-eth.hiveon.net:4444 (54.93.144.58)
2018.09.17:15:36:31.607: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x95e9f66fdb534213f9245d89a297e6192ddcf400.RIG-0","x"]}

2018.09.17:15:36:31.674: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":1}
2018.09.17:15:36:31.674: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:36:31.740: eths Eth: Received: {"jsonrpc":"2.0","result":["0x203e334f31c21cf1793d7aa9f30114a38e8164762129a6aacdf725e8ea105449","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:36:31.740: eths Eth: New job #203e334f from eu-eth.hiveon.net:4444; diff: 4000MH
2018.09.17:15:36:31.740: GPU1 GPU1: Starting up... (0)
2018.09.17:15:36:31.741: GPU1 Eth: Generating light cache for epoch #211
2018.09.17:15:36:36.404: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:36:36.474: GPU1 The option -clGreen 1 is ignored for GPU1
2018.09.17:15:36:36.483: GPU1 GPU1: Using new alternative OpenCL kernels (device name 'gfx804')
2018.09.17:15:36:36.483: GPU1 GPU1: Allocating DAG (2.66) GB; good for epoch up to #213
2018.09.17:15:36:36.483: GPU1 GPU1: Allocating light cache buffer (42.6) MB; good for epoch up to #213
2018.09.17:15:36:36.731: GPU1 GPU1: Generating DAG for epoch #211
2018.09.17:15:36:38.247: GPU1 GPU1: DAG  13%
2018.09.17:15:36:40.481: GPU1 GPU1: DAG  31%
2018.09.17:15:36:41.418: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:36:41.607: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:36:41.673: eths Eth: Received: {"jsonrpc":"2.0","result":["0x203e334f31c21cf1793d7aa9f30114a38e8164762129a6aacdf725e8ea105449","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:36:42.714: GPU1 GPU1: DAG  50%
2018.09.17:15:36:44.947: GPU1 GPU1: DAG  69%
2018.09.17:15:36:46.432: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:36:47.180: GPU1 GPU1: DAG  88%
2018.09.17:15:36:48.669: GPU1 GPU1: DAG generated in 11.9 s (227.2 MB/s)
2018.09.17:15:36:48.669: GPU1 GPU1: no gt value specified, switching to auto-tune
2018.09.17:15:36:48.669: GPU1 GPU1: starting auto-tune process
2018.09.17:15:36:51.447: main Eth speed: 7.684 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:36:51.607: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:36:51.607: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x753e7f","0x18f1223efa78b6d368f852c09af4936fad22da1f4715636b04c05714033100fa"]}

2018.09.17:15:36:51.674: eths Eth: Received: {"jsonrpc":"2.0","result":["0x203e334f31c21cf1793d7aa9f30114a38e8164762129a6aacdf725e8ea105449","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:36:51.674: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":6}
2018.09.17:15:36:53.012: eths Eth: Received: { "jsonrpc":"2.0", "result": ["0x55e2c67d8ed350c85a49de19cad4d914f17aa92e8f448231930cef9b838aca2a","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"] }
2018.09.17:15:36:53.013: eths Eth: New job #55e2c67d from eu-eth.hiveon.net:4444; diff: 4000MH
2018.09.17:15:36:56.460: main Eth speed: 9.193 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:36:59.468: main GPU1: 65C 100%
2018.09.17:15:37:01.473: main Eth speed: 8.035 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:01.607: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:01.674: eths Eth: Received: {"jsonrpc":"2.0","result":["0x55e2c67d8ed350c85a49de19cad4d914f17aa92e8f448231930cef9b838aca2a","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:37:06.486: main Eth speed: 7.782 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:11.499: main Eth speed: 8.408 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:11.608: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:11.608: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x833aea","0x18f1223efa78b6d368f852c09af4936fad22da1f4715636b04c05714033100fa"]}

2018.09.17:15:37:11.674: eths Eth: Received: {"jsonrpc":"2.0","result":["0x55e2c67d8ed350c85a49de19cad4d914f17aa92e8f448231930cef9b838aca2a","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:37:11.675: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":6}
2018.09.17:15:37:16.512: main  
2018.09.17:15:37:16.512: main *** 0:00 *** 9/17 15:37 **************************************
2018.09.17:15:37:16.517: main Eth: Mining ETH on eu-eth.hiveon.net:4444 for 0:00
2018.09.17:15:37:16.517: main Eth speed: 10.360 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:16.517: main 1 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2018.09.17:15:37:16.517: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2018.09.17:15:37:16.517: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00% 
2018.09.17:15:37:16.517: main Eth: Average speed (5 min): 9.063 MH/s
2018.09.17:15:37:16.517: main  
2018.09.17:15:37:21.532: main Eth speed: 11.322 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:21.608: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:21.674: eths Eth: Received: {"jsonrpc":"2.0","result":["0x55e2c67d8ed350c85a49de19cad4d914f17aa92e8f448231930cef9b838aca2a","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:37:26.545: main Eth speed: 12.011 MH/s, shares: 0/0/0, time: 0:00
2018.09.17:15:37:26.839: eths Eth: Received: { "jsonrpc":"2.0", "result": ["0x3579be5912882946a53b63c820227248be35a38403187d86f9255f35a5a9d435","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"] }
2018.09.17:15:37:26.839: eths Eth: New job #3579be59 from eu-eth.hiveon.net:4444; diff: 4000MH
2018.09.17:15:37:27.548: main GPU1: 68C 100%
2018.09.17:15:37:31.560: main Eth speed: 12.539 MH/s, shares: 0/0/0, time: 0:01
2018.09.17:15:37:31.608: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:31.608: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9d30f6","0x18f1223efa78b6d368f852c09af4936fad22da1f4715636b04c05714033100fa"]}

2018.09.17:15:37:31.678: eths Eth: Received: {"jsonrpc":"2.0","result":["0x3579be5912882946a53b63c820227248be35a38403187d86f9255f35a5a9d435","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:37:31.679: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":6}
2018.09.17:15:37:36.573: main Eth speed: 12.931 MH/s, shares: 0/0/0, time: 0:01
2018.09.17:15:37:41.588: main Eth speed: 13.066 MH/s, shares: 0/0/0, time: 0:01
2018.09.17:15:37:41.608: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:41.678: eths Eth: Received: {"jsonrpc":"2.0","result":["0x3579be5912882946a53b63c820227248be35a38403187d86f9255f35a5a9d435","0x95110ca8048b60699de72f2c00e65f06a5d8a088a64c146e5a8eb2827e1b1234","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"],"id":5}
2018.09.17:15:37:46.601: main Eth speed: 13.108 MH/s, shares: 0/0/0, time: 0:01
2018.09.17:15:37:51.608: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.09.17:15:37:51.608: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa838b0","0x18f1223efa78b6d368f852c09af4936fad22da1f4715636b04c05714033100fa"]}

[AlteregoX]

I'm on Linux and I just noticed Phoenix is slower than Claymore

Hope it's only because Linux version is new

Any advice? mining on NVIDIA

   It is possible but we need more information to check and solve the problem. Please let us know the Linux version, the version of the driver, and what cards you are using.

I'm using Ubuntu 18.04, 396.54, 1060 gtx.

[Bigdrago]

When turning the rig on and off the hashrate went from 408 to 401.
How is that possible. Is auto-tune that unstable?

[Soliqesh]

When turning the rig on and off the hashrate went from 408 to 401.
How is that possible. Is auto-tune that unstable?

Its new bug, you need restart system.

[salvo2002]

Shoutout for the Linux version!

I ran a comparison test for ~29hrs between PhoenixMiner and Claymore. Results here: https://forum.hiveos.farm/t/custom-miner-phoenixminer/7391/2

Keep up the great work PhoenixMiner Devs!

[Falconnn]

how to set -150 GPU Voltage in Phoenix miner, manuali can set in trixx
http://shrani.si/f/20/11j/opoHvUD/-150.png
i have 200W less consumption, 9 AMD cards use 1300W -1350w max elec, moded bios

[gsrcrxsi314]

how to set -150 GPU Voltage in Phoenix miner, manuali can set in trixx

i have 200W less consumption, 9 AMD cards use 1300W -1350w max elec, moded bios

read the Readme file. it tells you everything.

[PhoenixMiner]

   CLO is added already (since 3.0c), you just need to specify -coin clo and it will mine the devfee in CLO. As for MOAC - it will be added in 3.5d, which will be released later today or tomorrow morning.

Big thanks. Because it is pretty annoying when devfee switching DAG file 2 times.
P.S. any ideas why this command doesnt work with r9 280x card or it only support Polaris? -cvddc 1050 -cclock 1130 -mclock 1374  -fanmin 100 -powlim -15

   R9 280X uses older version of the Overdrive API, which isn't fully supported by PhoenixMiner. We will add this as well as many other hardware control features in PhoenixMiner 3.6 (and no, it won't take as long as 3.5, which was delayed a few times by some unexpected events).

@Pheonixminer -clgreen 1 works so good with RX 580/570 4gb memory, stable hashrate - lower power consumption , but with 8gb memory RX570/580 if i try this kernel my cards have chaotic hashrate, rig 309 mh/s with standart kernel, if -clgreen kernel 304-307, its normal? Logfile https://drive.google.com/file/d/1G4uknUONcpITDHQfBCJkrRx3HfdWaAPB/view?usp=sharing

   Yes, unfortunately it is not the same with every card. You can try changing (lowering) the core and/or memory clocks a little as this may help with the green kernels hashrate as strange as it seems. Another option is to try -clkernel 2 but it rarely has significant effect whenever the green kernels are used.

All my previous tests was made without clgeen. By the way, it looks like clgreen doesn't work with gfx804 (See 2018.09.17:15:36:36.474).

   You are quite right. So, we will enable the green kernels on gfx804 too.

I'm on Linux and I just noticed Phoenix is slower than Claymore

Hope it's only because Linux version is new

Any advice? mining on NVIDIA

   It is possible but we need more information to check and solve the problem. Please let us know the Linux version, the version of the driver, and what cards you are using.

I'm using Ubuntu 18.04, 396.54, 1060 gtx.

   We are testing with Ubuntu 18.04 now, it works fine with AMD cards. Please note that there is no support for hardware control options (-cvddc, -cclock, -mclock, etc.) under Linux, so you have to set the clocks with some other means.

When turning the rig on and off the hashrate went from 408 to 401.
How is that possible. Is auto-tune that unstable?

   Shouldn't be, we usually get the same gt values every time with maximum 1-2 gt difference between the runs. If you suspect that the auto-tune is the problem, just put the best found -gt values in your config.txt or in the command line.

Shoutout for the Linux version!

I ran a comparison test for ~29hrs between PhoenixMiner and Claymore. Results here: https://forum.hiveos.farm/t/custom-miner-phoenixminer/7391/2

Keep up the great work PhoenixMiner Devs!

   Nice to hear! We are already working on PhoenixMiner 3.6.

how to set -150 GPU Voltage in Phoenix miner, manuali can set in trixx

i have 200W less consumption, 9 AMD cards use 1300W -1350w max elec, moded bios

    You can use the -cvddc command-line option to specify the voltage in mV. For example, -cvddc 850 will set the core voltage to 850 mV.

[PhoenixMiner]

PhoenixMiner 3.5d is officially released. These are the changes since the last beta (3.5c):

• Added support for direct mining of MOAC, Ether-1 (ETHO), and EtherCC (ETCC) coins (see the -coin option in the first post of this thread)
• Small fixes for solo mining and advanced stats

The full list of changes since the last version 3.0c can be seen in the first post of this thread.

Here is the download link for PhoenixMiner 3.5d:

(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.5d_Windows.zip
    ===================================
   SHA-1: 135da8653f5fe5eb6981d24f5b754f191a00f14e
 SHA-256: 67b88760e98de13d30fc55de3a6d571f8ade9da26b74d32a29d50eb3b3480009
 SHA-512: 0a6ec07806297522f050e983ce6cc5c6ec345080cbb0550c58159527d7aee0845701735cd4bed3b6494592473cb7bc49042daab4befe3571491df73a71185c0d

    File: PhoenixMiner_3.5d_Linux.tar.gz
    ====================================
   SHA-1: 97cc81c4a8485725597fb3d14efd08c55b798bd4
 SHA-256: c757878d149f8d215ab71b3d00716ba620e28aab4f24115695851cc5c8f0565f
 SHA-512: 07b48067b75007c1f0795863321c54d5e273e3adf5eb0c55a33d4e95fa2cad24edf0c772c632eccc0fdcb89acf37092dd131059df014e05e9decf343464ba240

We are already working on PhoenixMiner 3.6, which will add hardware control for Nvidia cards under Windows, and for AMD/Nvidia cards under Linux, as well some other new features.

[Scorpio777]

PhoenixMiner 3.5d is officially released.

Thank You for Yours work!
I like this miner for its good performance and usability. But a few last weeks I have an issue during its work...When the miner try to connect with the developers pools it report an error and several minutes unsuccessfully try to connect to those servers. As a result - I'm loosing about 5% of my hash power during 24h(
For now I will wait for fixing this problem in my favourite miner (Or maybe I need to change/add some additional command in the miner configuration?).  
https://imgur.com/a/NV6cRfy

[lncm]

Great, just for the -leaveoc option, I'll upgrade from 2.9.

[Metroid]

I did a quick test for my friend about this new version, -clgreen reduces 1% power and 1% hashrate, mix of rx 5xx rx 4xx cards, normal standard mode 0.5% faster than claymore and it uses same power. Fan control still lacks understanding, -tt must be target temperature and if temperature was hit then lower fan speed by xx%, if target temperature was not hit then it should be max fan until target temperature is hit and right now is not like that, in claymore this works perfectly.

[N0pr3s3n7]

is anyone mining with 1060 gtx 3gb on linux ? It seems for me they are not working , miner just doesnt do anything - looks like it's not loading up dag , although under linux it's written i got 2.9 gb free. Any one with such issue ? thx

[PhoenixMiner]

PhoenixMiner 3.5d is officially released.

Thank You for Yours work!
I like this miner for its good performance and usability. But a few last weeks I have an issue during its work...When the miner try to connect with the developers pools it report an error and several minutes unsuccessfully try to connect to those servers. As a result - I'm loosing about 5% of my hash power during 24h(
For now I will wait for fixing this problem in my favourite miner (Or maybe I need to change/add some additional command in the miner configuration?).  
....

   There are no changes that could affect the devfee so most probably the problem is either with your network connection or with your configuration. From the screenshot it seems that the normal (main) pool connection doesn't work properly (the devfee log lines start with DevFee:, not with Eth:). To diagnose problem further, please send us the part of the log file when the problem has occurred .

I did a quick test for my friend about this new version, -clgreen reduces 1% power and 1% hashrate, mix of rx 5xx rx 4xx cards, normal standard mode 0.5% faster than claymore and it uses same power. Fan control still lacks understanding, -tt must be target temperature and if temperature was hit then lower fan speed by xx%, if target temperature was not hit then it should be max fan until target temperature is hit and right now is not like that, in claymore this works perfectly.

   Thank you for trying out the new version. We are working on the hardware control settings and they will be much better in the next release of PhoenixMiner.

is anyone mining with 1060 gtx 3gb on linux ? It seems for me they are not working , miner just doesnt do anything - looks like it's not loading up dag , although under linux it's written i got 2.9 gb free. Any one with such issue ? thx

   We have tested with 1060 3GB under Ubuntu 16.04 with Nvidia driver 390.67 and there were no problems at all. Please let us know your Linux version, Nvidia driver version, and send us the first few minutes from the log file in order to see what is going wrong in your case.

We have ordered three different RX550 from different makes, hopefully at least one will be with gfx804

Great news! I'm waiting at least 15 Mh/s

   One of the cards turned out to be Baffin again, but the other two are gfx804s! We have found the problem with the kernels, and the hashrate on RX550 will be much more competitive in the next version.

[bitcoin.dbi]

   We have tested with 1060 3GB under Ubuntu 16.04 with Nvidia driver 390.67 and there were no problems at all. Please let us know your Linux version, Nvidia driver version, and send us the first few minutes from the log file in order to see what is going wrong in your case.

What driver version you can suggest for AMD and Nvidia cards?
P.S. Using polaris, pascal, R9 Tahiti.