Search content
Sort by
Showing 3 of 3 results by aardria
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Thank you, it appears that the console freezing problem only manifests on Windows 10 ver 1709 or later, and we were testing on earlier Windows builds (we have disabled Windows Update on our test rigs). Now we are able to reproduce it reliably and we will find a fix.
Yes, I am on Build 1709 and good to hear you were able to duplicate the problem.
Quote from: Phoenixminer
We also ordered an RX550 so there will be optimized kernels for it in the next release.
Good to know you and looking forward to the release that is optimized for it. Having 1 or 2 might not be a big deal, but when you have 50, well do the math
Just an FYI, Claymore's new update states further optimization for the for the RX550 via (-asm) and it is! Your efforts are clearly being noticed so you've gotta bring your game face!
https://imgur.com/a/C9m30
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Yes. Using 2.7c
The Freeze with the "E" on the screen happens to me any time I try to scroll back.
Have to exit miner and restart it.
We will look into this, the problem is that it doesn't happen on our test rigs but we will find a way to reproduce and fix it. The Freeze with the "E" on the screen happens to me any time I try to scroll back.
Have to exit miner and restart it.
This is what happens on my end and no combination of keyboard entry (other than Ctrl+C ) does anything to bring the normal onscreen miner back. As another member has mentioned, the miner is still actually running in the background, and the logs actually confirms that it is running normally.
http://i121.photobucket.com/albums/o210/mrkookm/E_zpsfehhr1p7.png
http://i121.photobucket.com/albums/o210/mrkookm/Ctrlc_zpso1s9jfqb.png
...
I've been running the miner now for a few weeks and it's superb, except for the mentions below:
1) the miner doesn't seem to be optimized for the RX550's as attempts your miner with them the resulting hashrate is ~7+, while Claymore gets ~10+. Is it optimized for them and I'm doing something wrong, or can the you make it compatible if it's not?
...
Well, we don't actually have any RX550 cards here I've been running the miner now for a few weeks and it's superb, except for the mentions below:
1) the miner doesn't seem to be optimized for the RX550's as attempts your miner with them the resulting hashrate is ~7+, while Claymore gets ~10+. Is it optimized for them and I'm doing something wrong, or can the you make it compatible if it's not?
...
so it is probably running the generic kernels, which are slower. We will try get some and make better kernels for them for the next release.It is indeed using the generic Kernel:
http://i121.photobucket.com/albums/o210/mrkookm/Phoe550_zps6v8i9k6g.png
Resulting hash output:
http://i121.photobucket.com/albums/o210/mrkookm/Phoe5502_zpsjr0kvxgc.png
Claymore's resulting hash with RX550's:
http://i121.photobucket.com/albums/o210/mrkookm/Clay550_zpsgxspuvku.png
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Quote from: Phoenixminer
We show the momentary hashrate as it is (with very little filtering). However as there seems to be a lot of questions like this, perhaps we should use more filtering to smooth out the peaks and dips and show "nice" smooth hashrate average for at least 15-30 seconds. For those who want to see the momentary hashrate, there will be a commnad-line parameter to choose the time window for hashrate smoothing.
I like raw unfiltered output, so please ensure for those us who likes it as is to be able to disable the filtered output. It's been reliable for me (Amd's), and the layout and info it provides without me having to to touch my keyboard is wonderful! The little things..
I've been running the miner now for a few weeks and it's superb, except for the mentions below:
1) the miner doesn't seem to be optimized for the RX550's as attempts your miner with them the resulting hashrate is ~7+, while Claymore gets ~10+. Is it optimized for them and I'm doing something wrong, or can the you make it compatible if it's not?
2) scrolling the miner to review past output causes the miner to freeze or at least I thing it is. Doing so I get an E at the very last line and after having it sit for a few the normal 'hashing' output does not return, but if I do a Ctrl + C is gives the option to stop the miner without any hitch. Can you explain what's possibly happening?
Is anybody knows how fine tune works ? Bigger is better or how to find best value?
See Post # 474 & 483