Show Posts
...
appreciate the time comparing and clear justification, i am looking forward to see 2.9 outperform Claymore.
what i like about PM is that it could maximize my GPU's capability to hash up to 31.2Mhs for 580's which has a difference of .5 Mhs from Claymore.
having 1-2% of stale share is reasonable enough to shift to PM, i am still trying out other settings using PM though.
thanks and appreciate your feedback.
PhoenixMiner 2.9 should be released withing a few days (the internal test results for AMD cards are quite good but we are still tuning up the CUDA kernels).appreciate the time comparing and clear justification, i am looking forward to see 2.9 outperform Claymore.
what i like about PM is that it could maximize my GPU's capability to hash up to 31.2Mhs for 580's which has a difference of .5 Mhs from Claymore.
having 1-2% of stale share is reasonable enough to shift to PM, i am still trying out other settings using PM though.
thanks and appreciate your feedback.
PhoenixMiner I owe you a beer, my mistake in the comment where I suspected that there was a bag in your miner, and it was a MITM attack. Sorry ser.
Thanks a lot, we will drink a Heineken (or three) in your honor 
The SSL will get rid of these attacks, it's a pity that only ehtermine supports it yet - if fact, if it weren't for their initiative, the SSL support wouldn't happen for a long time.Any plans for CryptoNote miner or integration or a seperate miner?
Already answered here (sorry but we don't have more specific answer for now):Any plans for CryptoNote miner or integration, would be great?
Not in the immediate future but in a few months a lot could and probably would change. 
Hi Guys,
Can I specify the logfile name and maximum size (i.e. 75MB)?
Unfortunately not yet, but we will try to add this in 2.9 as it is overdue (it is sitting in our TODO list for at least a month).Can I specify the logfile name and maximum size (i.e. 75MB)?
I have question regarding to stale share:
I located in US, would my stale rate be higher if I connect to EU server than connect to US server?
I've been tested this many times with Claymore in a 24-hour continue mining period.
Connecting to US or EU, I forgot to record all the stale rate, but eth/hour stay nearly identical.
Theoretically, yes because the network latency will be higher. However, these things should be put in perspective. The average time between jobs on ethermine is about 12 seconds, so every 50 ms two-way round trip time increase would increase your stale shares by about 0.4% (50/12000). If you are mining a coin with bigger block time, the stale shares decrease proportionally.I located in US, would my stale rate be higher if I connect to EU server than connect to US server?
I've been tested this many times with Claymore in a 24-hour continue mining period.
Connecting to US or EU, I forgot to record all the stale rate, but eth/hour stay nearly identical.
Also I have another question regarding using -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580.
I used to be able to use them on claymore prior to blockchain beta driver. But ever since I upgrade to blockchain beta, the setting will no long stay very long. It is able to set them correctly via claymore, after mining for awhile, it will reset to default some the hashrate will drop, power usuage and temperature will go up as result.
Some people mention 18.3.4 driver fix the problem so I can use claymore 11.6 to control OC setting again like before. But I still haven't apply the new AMD driver yet because: 1) It took a lot of time to get driver correctly installed (2~3 hours, most times longer) 2) not sure the new driver is as stable as the old one (My rigs have been running for a month now w/o hang, so I don't really need to do anything to interrupt that streak unil something is broken)
Anyway, can I use -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580 with Phoenix 2.8c on Blockchain beta driver?
Yes but they will probably be unstable. The ADL support (which is responsible for the overclocking and voltage control) in the beta blockchain drivers is quite broken. Only the 18.x.x drivers fixed most of its problems. If you want to remain with the blockchain drivers the best way is to use MSI Afterburner or something similar to control the clocks and voltages.I used to be able to use them on claymore prior to blockchain beta driver. But ever since I upgrade to blockchain beta, the setting will no long stay very long. It is able to set them correctly via claymore, after mining for awhile, it will reset to default some the hashrate will drop, power usuage and temperature will go up as result.
Some people mention 18.3.4 driver fix the problem so I can use claymore 11.6 to control OC setting again like before. But I still haven't apply the new AMD driver yet because: 1) It took a lot of time to get driver correctly installed (2~3 hours, most times longer) 2) not sure the new driver is as stable as the old one (My rigs have been running for a month now w/o hang, so I don't really need to do anything to interrupt that streak unil something is broken)
Anyway, can I use -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580 with Phoenix 2.8c on Blockchain beta driver?
Hi Phoenix, FWIW, here's a small "potential bug" I found:
I use Monitorig to keep track of all my rigs:
https://bitcointalk.org/index.php?topic=1448855.0
Everything goes fine, except for single GPU rig, where for some weird reason Monitorig won't pick it up.
I'd be inclined to 'blame' Monitorig, but here's the catch: I switched all single GPU rigs back to Claymore, and they worked fine!
My guess: it has something to do with your log file format, because that's how Monitorig output the information.
***If you could please change/mimic Claymore's in your future updates, that'd be great!***
Thanks and keep up the good work! I have to switch back to Claymore for now for single GPU rigs though
Unfortunately, this is quite unlikely to happen because: a) we would be unable to add new statistics and information and we have such plans; and b) a lot of users actually like our console output better, so we would be giving up one of our advantages. Hopefully, in time most remote control and monitoring applications will support PhoenixMiner fully (there are a lot that support us already but not all).I use Monitorig to keep track of all my rigs:
https://bitcointalk.org/index.php?topic=1448855.0
Everything goes fine, except for single GPU rig, where for some weird reason Monitorig won't pick it up.
I'd be inclined to 'blame' Monitorig, but here's the catch: I switched all single GPU rigs back to Claymore, and they worked fine!
My guess: it has something to do with your log file format, because that's how Monitorig output the information.
***If you could please change/mimic Claymore's in your future updates, that'd be great!***
Thanks and keep up the good work! I have to switch back to Claymore for now for single GPU rigs though
Hi there
I added one more Ellesmere card to my rig (4 now) and Phoenix Miner stopped controlling fan speeds.
-tt and -fanmin stopped working.
I tried to use only one value or assigning a value to each card, but it won't work.
Claymore's works as usual.
Any ideas?
If you are using the blockchain drivers, all bets are off. If you are using 18.x.x drivers, please tell us the model of the card that is giving you problems (and the version of the driver).I added one more Ellesmere card to my rig (4 now) and Phoenix Miner stopped controlling fan speeds.
-tt and -fanmin stopped working.
I tried to use only one value or assigning a value to each card, but it won't work.
Claymore's works as usual.
Any ideas?
HI Dev,
can you put genom coin to the devfee list to avoid dag switch?
Will try to add it in the next release.can you put genom coin to the devfee list to avoid dag switch?
Can someone help to resolve this error?
I had internet connection problem and after connetion went up again, the miner did not connect again.. I had to restart miner.
Is there any resolve for this issue? Why is phoenix connection to port 4444 nad not 5555 ssl?
You have forgotten to change the wallet address from the default YourWallet in the example command lines. Ethermine doesn't like the invalid ethash address (obviously YourWallet is not a valid ethash address) and disconnects with error "Invalid user provided". After three unsuccessful attempts, the miner switches to the next pool, which is not using SSL. To fix the problem, paste your real ethash address into the command line (or in the epools.txt file).I had internet connection problem and after connetion went up again, the miner did not connect again.. I had to restart miner.
Is there any resolve for this issue? Why is phoenix connection to port 4444 nad not 5555 ssl?
Code:
17628:09:32:51.214: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555
17628:09:32:51.214: unkn Eth: Giving up after 3 retries, switching to next pool
17628:09:32:51.214: unkn Eth: Reconnecting in 20 seconds...
17628:09:32:55.514: GPU2 Unable to submit share - pool disconnected
17628:09:33:04.989: GPU3 Unable to submit share - pool disconnected
17628:09:33:09.973: GPU4 Unable to submit share - pool disconnected
17628:09:33:11.222: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:33:11.256: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.239.100)
17628:09:33:11.256: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:33:11.277: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:33:18.794: main GPU1: 54C 72%, GPU2: 54C 56%, GPU3: 49C 49%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 43C 70%
17628:09:33:21.952: GPU2 Unable to submit share - pool disconnected
17628:09:33:43.568: GPU5 Unable to submit share - pool disconnected
17628:09:33:46.704: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 43C 70%
17628:09:33:55.839: GPU4 Unable to submit share - pool disconnected
17628:09:34:04.807: GPU4 Unable to submit share - pool disconnected
17628:09:34:09.682: GPU5 Unable to submit share - pool disconnected
17628:09:34:11.873: GPU5 Unable to submit share - pool disconnected
17628:09:34:14.941: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 55C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:30.878: GPU3 Unable to submit share - pool disconnected
17628:09:34:42.992: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:48.490: GPU3 Unable to submit share - pool disconnected
17628:09:34:51.279: eths Eth: Connection closed by the pool
17628:09:34:51.279: eths Eth: Reconnecting in 20 seconds...
17628:09:35:11.097: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:35:11.285: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:35:11.308: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.226.213)
17628:09:35:11.308: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:35:11.329: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:35:22.780: GPU6 Unable to submit share - pool disconnected
17628:09:35:39.343: main GPU1: 54C 73%, GPU2: 54C 57%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 42C 70%
17628:09:36:02.016: GPU4 Unable to submit share - pool disconnected
not sure if already mentioned but there is an typo when starting your miner
Oops, thanks for catching this 
I found a bug: if I start Claymore CryptoNight with some card and then start PhoenixMiner with all the other card then Phoenix crash...
I tried then to start first Phoenix and then Claymore and I saw the problem: I was using the same port (3333)... opsss I forgot to change it!
So if the port 3333 is busy PhoenixMiner crash.
I have also a request: can you add to the line of server name also the time when the connection occurred (or a counter)? I ask it because some time my internet connection go down and then up and I need to search on the log if this happened
*** 0:50 ***************************************************
Eth: Mining ETH on eth-eu1.nanopool.org:9999 from 13:00:00 07/04/2018
Eth speed: 183.484 MH/s, shares: 57/0/0, time: 0:50
I'm using your software from a few months and I'm very happy... I'm waiting for version 2.9!
Thank you for using PhoenixMiner! We will add the time and date as requested. As for the second problem, we have tested in such scenario and it shouldn't crash but print an error message. We will investigate further and fix the problem in the next release.I tried then to start first Phoenix and then Claymore and I saw the problem: I was using the same port (3333)... opsss I forgot to change it!
So if the port 3333 is busy PhoenixMiner crash.
I have also a request: can you add to the line of server name also the time when the connection occurred (or a counter)? I ask it because some time my internet connection go down and then up and I need to search on the log if this happened
*** 0:50 ***************************************************
Eth: Mining ETH on eth-eu1.nanopool.org:9999 from 13:00:00 07/04/2018
Eth speed: 183.484 MH/s, shares: 57/0/0, time: 0:50
I'm using your software from a few months and I'm very happy... I'm waiting for version 2.9!
17617:12:22:59.708: main Phoneix Miner 2.8b Windows/msvc - Release
17617:12:22:59.708: main Cmd line:
17617:12:22:59.708: main config.txt: -pool eu1-etc.ethermine.org:4444 -pool2 us1-etc.ethermine.org:4444 -wal 0xd07e049700388d961068b92e28a9a86064b67986.letjen2 -clkernel 2 -amd
17617:12:23:00.302: main Available GPUs for mining:
17617:12:23:00.302: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.330: main ADL library initialized
always stuck like that. From v6 to v8b, how to fix it? Let me know, tk u
17617:12:22:59.708: main Cmd line:
17617:12:22:59.708: main config.txt: -pool eu1-etc.ethermine.org:4444 -pool2 us1-etc.ethermine.org:4444 -wal 0xd07e049700388d961068b92e28a9a86064b67986.letjen2 -clkernel 2 -amd
17617:12:23:00.302: main Available GPUs for mining:
17617:12:23:00.302: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.330: main ADL library initialized
always stuck like that. From v6 to v8b, how to fix it? Let me know, tk u
I still have the same problem when i install a new windows version i have 7 rigs 3 of them don't want to work with phoenix after a new windows instalation and the other 4 works fine tell me please where is the exactly problem and how to bypass it and if it need install some package tell me please
Waiting for your reply devs
PhoenixMiner we are waiting 2.9, any news? 
Will be ready in a few days. We want to be sure that everything works fine as there are a lot of changes in the kernels.Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Please send us the log file and check if the miner shows "Debugger detected" error before crashing (the "Debugger detected" error will not be printed in the log file). If the console window closes fast after the program crashes, please put a pause command after the line that starts PhoenixMiner in your .bat file (or use the start_miner.bat file that is in the PhoenixMiner .zip file, which already has a pause command).Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
If the error is "Debugger detected" try to add -nvidia to your command line.
This is my problem and i added -amd too
http://prntscr.com/j2gt6n
Please i want to bypass this problem
Thanks in advance
