Quote from: rockk on January 29, 2018, 12:46:23 PM

2.5D seem to have hash rate inconsistensies compared to 2.4 . sometimes hash rate drop big time for some cards, 5mhs or so , compared to 2.4

The only thing than can be possibly linked to this is the new OpenCL initialization code (if you are using AMD cards?). We will make it optional in the next version if there are more reports of such behavior as the solved problem by the new code (occasional crashes on startup) is quite rare.

Quote from: Khan3388 on January 29, 2018, 03:52:16 PM

Hii
I have Radeon RX 570 GPU's and i have problem with PhoenixMiner 2.4 and 2.5d on Windows 10
I try with drivers : Adrenalin 17.12.2 and Adrenalin 18.1.1
On Windows 7 with Adrenalin 17.12.2 and Adrenalin 18.1.1, PhoenixMiner 2.4 and 2.5 works fine

Thank you for the log. As you have the same problem with both 2.4 and 2.5d, this isn't caused by the new OpenCL initialization code. OpenCL error -6 is CL_OUT_OF_HOST_MEMORY, which probably means that you have to increase the size of your page file to at least 16 GB. Let us know if the increasing of the page file size (you have to restart Windows after that in order to apply the changes) doesn't solve the problem.

Quote from: ANewMiner on January 29, 2018, 04:52:33 PM

I looked forward to 2.5 as I had problems like the others with it not making connections
...
but
...
2.5d doesnt seem to be working quite right either, unless now at least it will continue with the connection it had.

We tested with the same devfee pool by disabling all others (eth-eu2.nanopool.org:9999) and it worked fine. Probably a temporary connection issue. Furthermore, 2.5d has at least one backup devfee pool (and in most cases two), so this shouldn't be a problem.

Quote from: jendabenda on January 29, 2018, 06:16:28 PM

guys I have to say I am bit disapointed that you can develop kernel that can run radeons about 2-3% better (for me its about 20USD per day) But you cant contact pool providers to inform them about new miner.... Its quite logical that when your miner got popular it raised red flaggs on pool. Its like botnet when so many IP adresses are mining for one wallet.... And also you should heve issued warning ASAP not to use it until you make it right with pools.

At first we though that ethermine was having difficulties with the spike in Ethereum hash power lately. As soon as we realized that the block is targeting our miner, we published a warning message here. You are probably right and we should have tried to contact them beforehand but it's a bit of chicken and the egg problem - if (almost) nobody uses our miner why should they believe us and white-list us just based on our word? Additionally, outright blocking IP-s is probably not the best way to deal with a potential botnet. Perhaps it would be better to just "shadow-ban" the suspicus devfee-like connections and accept shares as normal but don't credit any coins to these addresses. In this way if the connections are from malicious software, the bad guys would give up because there is no upside to continue. And if it is a legitimate miner as ours, it would only affect our devfee, not the users of our miner, which was way, way worse.

Anyway, it seems that the issue is fully resolved now - ethermine and ethpool work normally with PhoenixMiner (even the older versions). Kudos to ethermine for reacting so quickly, they really are top notch. Unfortunately the few bad apples in this business make the life harder for everybody else.

Quote from: ANewMiner on January 29, 2018, 10:46:50 PM

I also wish I was younger, I used to code a lot.. Id also have taken a stab at building a miner, package it up so its a service, quietly doing its thing.. its not like I dont know how to code for linux and windows.. Im sure I could have done something but now Im older i get home and the enthusiasm just has worn out..

Quote from: Branko on January 29, 2018, 11:28:32 PM

I did 6502 and Z80, I'm THAT old Grin

Our average age is closer to 40 than to 30 Grin

It is fun but the last two days (and nights) were anything but. There was a lot of swearing, hair pulling, and face-palming in our office. To continue the side note, one of our programmers is really into retro computing. His house is like a computer museum. His remark: "6502 wasn't fun to write for, 8080/Z80 was much better, and when the IBM PC came out, the 8088 assembly was like writing in high-level language, compared to 6502".