Quote from: wip on February 14, 2018, 02:21:44 PM

Hello team,

Would there be any particulaur reason if 3stale shares was received miner jumps directly to backup pool?
I can understand if we get X amount of rejected shares, but stale shares.

There is no code to switch pools based on number of stale shares. Probably the pool closed the connection after X rejected shares (some pools reject all stale shares) and the next three attempts to reconnect were not successful. After 3 failed attempts to connect to a pool, PhoenixMiner switches to next pool in the list. If you haven't set the option -ptimeout 0 (or -ftime 0), PhoenixMiner will try to switch back to the primary after 30 minutes of mining on the backup pool.

Quote from: cmd_whoami on February 14, 2018, 01:32:22 PM

@PhoenixMiner - Looks like the issue is with the odd card of the rig, the Zotac 1070 Ti AMP Edition. I added that 9th card when Windows did the fall creators update allowing Windows to find more than 8 cards. The other 8 are Zotac 1070 AMP Extremes with a fan speed of 35%. The 1070 Ti, GPU4, GPU5 in Phoenix, is in the GPU4 location of my OC tool ( Nvidia Inspector 1.9.7.8 ) with a fan speed of 49%.

NVML usually reports the GPUs in the same order as CUDA but apparently not always. We will add some workarounds but the problem is how to detect this case at all by the miner itself.

Quote from: JoepMeloen on February 14, 2018, 10:37:56 PM

I like it sofar.. i love the altcoins devfee.. stupid CM devfee is crashing my rig alot.

one very important question though..

How to set target temp? -tt 65 doesnt seems to work and gpus are running way to hot, up to 80C. CM can keep them nicely on the targettemp..how to do this in PM?
~~also: -cclock and -mclock etc doesnt take and there pretty important to finetune the rig.~~ (just read your comment about it)

im using awsome miner (with PM as user added software)and need the cmd's -tt , cclock, -mclock. mostly the -TT !

Awsome miner also doesnt show info about the miner, any clue why not? (it does show the console)

also: get this into Awsome Miner !

We hope to get official support in Awesome Miner but it's not up to us. If enough people request support for PhoenixMiner, it will probably be included as officially supported miner. As for the -tt (and the other hardware control options), we are currently working on them and a beta version with support for them will be released in a few days.

Quote from: Yellow_donkey on February 15, 2018, 03:03:30 AM

I just tried it and no go. Please confirm that solo mining/direct mining to geth or parity remains a non-feature with 2.7a. Thanks.

Yes, solo mining (proxy mining) will have to wait for the final 2.7 release.

Quote from: PcChip on February 15, 2018, 03:34:06 AM

FYI - 2.7a still says debugger detected on my 1080Ti desktop PC
I have Visual Studio 2017 installed, making SDL2 c++ apps - perhaps something there caused it ?

No, Visual Studio is not the issue - we have VS on all our machines and no problems. Please try to add the command-line option -nvidia - others have reported that is solves similar problems.

Quote from: Tranzius on February 15, 2018, 06:29:35 AM

Testing 2.7a from yesterday and so far OK.

However I detect difference in stale shares reporting. The miner reports 0 stale shares in one hour, but pool shows 4 stale shares - mining on ethermine.
Also effective hashrate reported in command line does not match with web reported hashrate on Ethermine.

Bug with DevFee and reseting cards voltages is fixed.
Hashrate is compared to claymore for about 1-2% better.

There is no difference in stale share reporting in 2.7a but we have increased the frequency by which we ask the pool if the job has changed. This slightly lowers the chance of stale shares that are detectable by the miner itself but it has no effect on the stale shares that come from pool and/or network latency. We have no way of detecting the later - please see answers Q005 and Q008 in our first post in this thread. Because even the pools that accept stale shares (like ethermine) credit them lower than normal shares, the effective hashrate at the pool is lower. In our estimation ethermine credits the stale shares at about 60% of normal shares, so if you have 10 stale shares, they count only as 6 normal shares, and if your total number of shares per hour is 200 (190 normal and 10 stales), you will have effective hashrate 217 MH/s reported by the pool instead of 222 MH/s (these numbers are based on share difficulty 4000 MH).

Quote from: torgamer on February 15, 2018, 12:32:16 PM

Hi

I have problem with eth-proxy
Phoenix miner stuck at Starting GPU Mining

please help

The current version doesn't support solo (proxy) mining. This feature will be added in the final release of 2.7 in about a week or so.

Quote from: flatounet on February 15, 2018, 09:07:47 PM

POOL: eth-eu1.nanopool.org:9999

dont look work ,

i just want have the same commande / option like the bat file
but with all nanopool mirror (nano have 7 mirror )...

eth-eu1 , eth-eu2 .....

im sorry ,it dont look clear for me Sad

and may be add more mirror if all nanopool was dead ,switch to another one ( flypool ... )

can you put sample for config.txt & epool.txt in FP like for bat file ?
thank's you

You can use the config.txt and epools.txt files that nanopool configure tool generates for Claymore Dual Miner - they should work with PhoenixMiner without any changes. If you want to use these files, start the miner directly (by double-clicking PhoenixMiner.exe) instead of using the start_miner.bat file. If you want to add additional pools, you can add them into epools.txt (there is no limit on the number of pools there).