Quote from: Metroid on March 12, 2018, 06:39:00 AM

Quote from: PhoenixMiner on March 12, 2018, 06:23:31 AM

Could you tell us what version of AMD drivers you are using and what behavior of the fans you are observing? We definitely can and will make improvements in the hardware control options but we need more information to troubleshoot any problems.

Blockchain 23 august 2017, it works like this -tt 60 -fanmin 85 -fanmax 85 -tmax 80, the problem about this is the fan will never be silent if the miner is not mining cause the min is 85%. On claymore you just need 2 commands to work -tt 60 -fanmax 85 cause as the fans will be at full speed since beginning to reach the 60c temp, once the fan reaches 60c then it lowers decrease the fan speed if less than 60c. So claymore is better in that sense.

Thank you for the information. The blockchain drivers definitely doesn't work properly with our way of controlling fan speed and voltages (only the clock settings seem to work properly and reliably). The new drivers (18.x.x) have fixed almost all bugs in fan speed control (without any significant hashrate changes) so you can try them and see if they solve the problem for you.

Quote from: StreetER on March 12, 2018, 07:23:05 AM

such a function is very necessary that would work without restarting the miner, this is like selecting the server in epools.txt while the miner is running, only with automatic switching and indicating how long and which wallet

Yes, this could be useful in some cases but we have a lot on our plate and it may take a while before this is implemented.

Quote from: MiningTaken on March 12, 2018, 08:26:52 AM

@PhoenixMiner,

I run PhoenixMiner 2.7c on 6 x GTX1070 Ti (Win 10 Pro build 1709) smoothly, until these last several days.
Every time after I run it for several minutes, one of my cards suddenly lost its memory OC setting and back to is default memory setting.
It happens when the miner restart, right after it crash (after connection error to "d3pool.eu/api/status").
I tried to ping "www.d3pool.eu", but the connection is okay and no packet loss.

Here is what I found in the log file :
...

Please help. Thank you.

We need the log file of PhoenixMiner itself in order to make any conclusions. This log file doesn't contain any information that would tell us why the program is crashing or closing.

Quote from: derdigge1982 on March 12, 2018, 09:49:00 AM

Sorry for not reading all 50 Pages.

Is there a linux Version yet?

Thanks.

Not yet. Rest assured, whenever it's ready, it will be posted on the first page (and even on thread's title).

Quote from: aneumoin on March 12, 2018, 10:34:03 AM

PhoenixMiner 2.7c
1050TI
last nvidia driver

C:\Miner\PhoenixMiner>PhoenixMiner.exe -pool asia.ethash-hub.miningpoolhub.com:20535 -wal aneumoin.eth1 -pass x -proto 1 -mi 12 -log 0
Phoneix Miner 2.7c Windows/msvc - Release
-----------------------------------------
...
does not find shares.
Switching pools does not help
such a situation the last few days
why so little shares finds?
15.8 MH/s the speed is quite sufficient

This is just bad luck, nothing wrong with the log.

Quote from: infectedmushi on March 12, 2018, 11:22:54 AM

@PhoenixMiner

is it possible to check what wrong with the the API used for monitoring apps, like "Claymore's miner monitor" by SIRIUS for android (currently at version 19.0214.P) ..?

It works fine with claymore, i get all gpu's temperatures, shares, uptime etc.. using PhoenixMiner, i only have access to miner log on port 3333, nothing else.

Same happens with other similar apps.

Thanks in advance.

We support the monitoring JSON API of Claymore but some programs may try to parse the log messages themselves, which obviously are quite different in PhoenixMiner. We are adding support for miner_getstat2 request too, which was missing in the current versions, so this should improve the compatibility.

Quote from: MaxMidnite on March 12, 2018, 05:14:27 PM

When is the next update and what can we expect, wish to use this miner?

In about a week there will be a beta release (maybe even sooner if no issues are found during the internal testing). There will be a lot of small improvements; support for -li, -tstop, and -tstart options; and some other changes...

Quote from: skinnyfalcon on March 13, 2018, 12:57:31 AM

@PhoenixMiner

During the process of optimizing the OC settings I discovered the following bug:

After mining stable for a while the miner was stopped,
in the process of changing the memory clock setting from

-mclock 2150,2150,2150,2200,2125,2200,2150,2150

to

-mclock 2150,2150,2150,2200,2150,2200,2150,2150

and restarting the miner, the hash rate for GPU5 showed no change as a result of the clock increase. However, when the rig was rebooted, the hash rate now reflected the clock change.

It would appear that restarting the miner after setting changes (in this case the miner clock, may be true for other parameters as well) does not apply these changes (write to the hardware). Only rebooting Windows affected the change.

I am running:
Windows 10 1709
AMD 18.3.1
8 x RX580 8 GB

The problem is that there is no reliable way to get the default settings, without resetting all settings to the defaults. PhoenixMiner resets the settings to the default only if a "clean exit" is made with Ctrl+C in the command console. We can also reset the settings on startup but this may interfere with any other programs that are used for control of clocks/voltages/fans, etc. Perhaps the best way is to add an option -hwclean or something like this, which to tell PhoenixMiner that it is OK to reset the settings on startup.

Quote from: carlotech on March 13, 2018, 02:49:17 AM

Phoneix Miner 2.6 Windows/msvc - Release
----------------------------------------

....
Eth: Connection closed by the pool
Eth: Giving up after 3 retries, switching to next pool
Eth: Reconnecting in 10 seconds...

any help from phoenix team?
2.6 and 2.7c
everything is working until it stops getting shares from the pool. tia

This seems like a connectivity problem - the connection is established and then closed by the pool.

Quote from: kdminhkhanh on March 14, 2018, 01:09:48 AM

I Used ver 2.7c and and I was error 999.
https://i.imgur.com/46nKKyN.jpg

This is typically result of too much memory overclock. Lower the memory overclock on this card by 20-30 MHz and the problem should go away.