Quote from: Yarik47 on June 12, 2018, 06:25:18 AM

Hello guys, hello PhoenixMiner.
I decided to try the phoenix miner, I liked it, the speed of hashing is slightly larger than on the claymore. But after 9 hours the speed of the farm 5*msi GTX1070 GamingX 32Mh/s fell to 27, and the second farm 5*msi GTX1060 GamingX 6Gb completely disconnected with an error(cuda error 749) .. What's the problem?
And yet - my farm 5* RX550 4Gb, in the claymore they show 13.8 each, and the phoenix miner is only 12.5. What is wrong I do?
P.s. sorry for my English))

Please check the clocks, voltages, and fan speeds on your cards because PhoenixMiner doesn't support setting clocks and voltages on Nvidia cards. So if you were using Claymore for controlling these, you'll need to use a third party program with PhoenixMiner. We are going to implement support for setting the clocks, voltages, and fan speeds for Nvidia GPUs in a future version.

Quote from: driccardi92 on June 12, 2018, 10:16:01 AM

Works like a charm. Is there any Powerlimit command line for Nvidia?

Not yet, will be added in the future. For now you'll have to use Afterburner or something like this.

Quote from: StreaMeX on June 14, 2018, 04:46:24 PM

We're trying to integrate this new miner with our python monitoring system, and it does not seem to receive any socket response.

Documentation for PhoenixMiner claims that it uses same api approach as Claymore.

Here's our code:

Code:

TCP_IP = '127.0.0.1'
TCP_PORT = conf("MINER_API_PORT")
BUFFER_SIZE = 1024
MESSAGE = '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}'

log.debug ("{}:{} - {}".format(TCP_IP, TCP_PORT, MESSAGE))
log.debug("Socket creating...")
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
log.debug ("Socket connecting...")
s.connect((TCP_IP, TCP_PORT))
log.debug("Socket sending request...")
s.send(MESSAGE.encode('utf-8'))
log.debug("Socket receiving response...")
data = s.recv(BUFFER_SIZE).decode('utf-8')
log.debug ("Claymore API Response: {}".format(str(data)))
log.debug ("Socket closing...")
s.close()

result = json.loads(data)['result']

It works perfectly well with Claymore, but it gets stuck at "Socket receiving response..." with Phoenix miner. So it seems it does not receive any data from socket connection. I could not find any detailed documentation on Phoenix's api, other than a statement that "it is the same as Claymore protocol".

Please, help - did I miss anything in documentation, is there a more complete documentation or how should I fix the code to work with Phoenix?

Thanks for your time and attention.

As already mentioned above, you'll need to add a new-line character and the end of your JSON-PRC request.

Quote from: steve8lily on June 15, 2018, 01:08:02 PM

Win10 Pro detect the software with trojon virus, pls advise

TLDR version: false positive caused by the anti-debug code in PhoenixMiner; we tried to contact AV software makers to fix this, some responded, most didn't. The best solution: add the folder where you keep your mining software in the "exclusions list" of Windows Defender or whatever AV software you are using. Also, it's a good idea to check if the checksum of the downloaded archive is the same as the one published here.

Quote from: Teti2347 on June 16, 2018, 07:42:23 PM

Hey Im hoping someone can help me out with an "out of memory" error I keep getting. I have a rig with the following build:
8 X NVIDIA 1070s
Asus H270-P motherboard
2X EVGA 750 PSUs
Windows 10
120 GB harddrive
8GB RAM

I am mining with PoenixMiner and using Nanopool and keep getting an error message. (I have 2 other rigs built the exact same and havent had any issues with them). Yesterday it was mining fine and the the program launched out, so I reset the rig and have been having issues since. I was able to get 7 GPUs running before but when I plugged in the 8th card, its giving me an error code. I tried switching out the risers and now am only able to get 6 cards working before the same error occurs -- "CUDA error in CudaProgram.cu:377 : out of memory (2)"

MSI Settings:
Power: 64
Temp: 67
Core Clock: 0
Memory Clock: 585

Any ideas??

Almost 100% sure that the problem is the size of the page file. Increase the page file size by 5-10 GB and you should be fine. As a rule of thumb the page file must be big enough to fit the DAGs of all cards plus another 5-10 GB for Windows stuff, so if you are using 8 cards and the DAG is about 2.6 GB, you'll need page file size at least 24 GB.

Quote from: jewbsv on June 19, 2018, 04:52:23 AM

Hi PhoenixMiner!
There was a problem with the miner on the https://etherdig.net pool with 1080ti graphics cards on port 4444.

Code:

PhoenixMiner.exe -epool etherdig.net:4444 -esm 3 -ewal YOUR_ETH_ADDRESS.RIG_ID -epsw x

Miner every 1 hour 23 (25) minutes and not earlier sends errors "Rejected", etc in a circle. If you turn off the miner, then again in 1 hour 23 (25) minutes will go the error "rejected."
This is something related to devfee. This is exactly with the 1080ti cards.
Check, please.

Will check but seems strange. The first devfee period is sooner than even 1 hour and the next is 90 minutes after that so 1:23 h seems like an odd time to be something related to devfee.

Quote from: lesjokolat on June 19, 2018, 01:56:52 PM

Dear PM I was just wondering what is differnece between Kernels 1(optimized)? and 2(alternative)? Are they specific to any type of GPUs?
Thanks

The optimized (-clkernel 1) kernels try to minimize resource usage and to allow the GPU to try "juggling" a few interleaving hardware threads in the same computing unit, while the alternative kernels try to use "manual" control over the way the threads are scheduled to run on the CU. In theory the first one should always be better (or at least not worse) than the second but ethash is so much limited by memory bandwidth that this is often not the case and the alternative kernels are faster instead.

Quote from: wotteam on June 19, 2018, 07:48:31 PM

I like the miner but it crash on my every time after the dev fee

2018.06.19:20:50:52.316: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.06.19:20:50:56.320: main Eth speed: 50.146 MH/s, shares: 9/0/0, time: 0:19
2018.06.19:20:50:59.332: main DevFee: Disconnected and stopped
2018.06.19:20:50:59.847: GPU1 GPU1: Starting up... (0)

Any hints?

It seems like it starts creating the DAG again and for some reason the GPU is crashing during the DAG generation. You should try using the -coin option to "tell" PhoenixMiner what coin you are mining because it seems it doesn't detect it correctly.

Quote from: Yarik47 on June 19, 2018, 07:52:58 PM

Hi
who then can know why the average speed and the effective speed are so different? I have an average speed of 160, and an effective 144 ..
5 * GTX1070
bat - PhoenixMiner.exe -pool etc-eu2.nanopool.org:19999 -wal -nvidia
pause

Let it run for about 24 hours and check again, the difference should be significantly less than that (like at least firmly above 150 MH/s).

Quote from: area511 on June 20, 2018, 08:04:18 AM

Why it still shows "eth" when mining "etc". I have set the parameter -coin etc but everything is still showing eth. Otherwise it's running fine on the pool.

Eth is used as prefix for messages that deal with ethash mining (eth, etc, and all other coins are using ethash). It is a bit redundant at this time but at some point when we finally introduce dual mining, this will help separate the messages for the primary and the secondary algorithm.

Quote from: human75 on June 20, 2018, 08:59:27 AM

Quote from: Metroid on June 20, 2018, 08:47:26 AM

The PhoenixMiner 3.0c always crash at start, windows 10 anniversary, only way to work is to set compatibility to windows 7 on properties, the other versions before this one did not have this problem.

One of my rig which has got mixed cards rx570, 580 and nvidia. version 3 is crashing just before dag creating starts.. i couldn't figure out why? 2.9 works smooth. strange problem

Can you please send us the log? A lot of things changed in 3.0 so it's hard to determine what's causing this without a log.