Quote from: darkCryptoMiner on June 18, 2019, 09:07:46 AM

Thanks!

Are you planning on including the AMD Mem tweaker in the next release?

For now - no, it works fine as free standalone program and we don't see much value in integrating it within the miner. However this may change in the future.

Quote from: biospb on June 18, 2019, 09:14:39 PM

Please fix support for newer drivers on linux - 19.10, 19.20.
currently miner uses -clnew 0 regardless of clkernel setting.
probably all these kernels can work if there was no check for driver version.

There will be full support for the latest Windows and Linux AMD drivers in PhoenixMiner 4.3.

Quote from: biospb on June 18, 2019, 09:14:39 PM

second thing that can be easily fixed - auto-tuning is quite slow and it is running after gpu temp reaching its limit. every time!
there is no need for this. just use gt values found during startup.

thanks in advance

It is deliberately "slow" (it takes 3-5 minutes on average) in order to get repeatable and reliable results. If the auto-tuning is significantly faster, we will be taking less measurements and as a result the "best" GT found may not be optimal. To avoid the problem you are running into, you can run auto-tune again after the temperatures has stabilized. In order to do that, you need to press the 'z' in the miner console window.

Quote from: WARMANGALAXY on June 19, 2019, 05:42:26 PM

зaмeчeнн бaг нa пpoтяжeнии 2-3 мecяцeв, Baш мaйнep пepeключaeтьcя нa ethermine pool и кaпaeт нecкoлькo минyт бeз dev fee a пpcoтo caм пo ceбe. пpoиcxoдит этo c пepeoдичнocтью c 3-5 cyтoк. зaмeтить oчeнь тяжeлo.

If our translation is correct, what you are observing is that PhoenixMiner switches to the secondary pool when the primary pool fails. PhoenixMiner always reads epools.txt file if there is such file, and adds the pools from it to the pools specified on the command-line. The epools.txt file that is supplied with the miner contains an example pool and address, which is used as fallback pool if you don't change it to your own. Here is what to do in order to fix the problem (you need to do only one of the following):
1) Delete or rename the epools.txt file which is in the same folder as PhoenixMiner.exe
2) Or, edit the epools.txt file and change the pool and wallet to your own secondary pool and wallet

Quote from: xsoft on June 19, 2019, 09:29:56 PM

Hi,
Im on "Phoenix Miner 4.2c Linux/gcc - Release build".

And and AMD RX470 I have an issue that after a while (hour) the miners freeze and stops mining.
Its not able to kill it (even with -9).

Restart helps, but to make a restart every hour is akward. This is happening to kinda all RX470. On RX480, 580, .. they are all fine. Same settings and version.
Ive also tried "-altinit -gser 0". Since without it the RX470 soing event start to mining.

Any tips?
(eh, last ethos and miner).

Code:

ethos 2705 0.0 0.0 0 0 ? D 20:50 0:00 [PhoenixMiner]
ethos 7716 0.0 0.9 186792 38336 ? Ds 20:50 0:00 /opt/miners/phoenixminer/PhoenixMiner -altinit -gser 0 -proto 2 -amd -worker ...

Unfortunately, no. There is no almost no difference in the way PhoenixMiner threats 470 and 570. The only possible explanation is that 470s are probably older and may experience some performance degradation, and may not be stable anymore on the clocks and voltages they were stable in the past. You can try to run them on lower clocks (mostly memory) and see if the stability issues remains. Another possibility is that the ambient temperatures are rising, and the cooling may not be enough (or the heatsinks may be clogged with dust, the thermal pads on the VRMs or memory chips may be drying and no longer being effective in conducting heat, etc).