Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 454. (Read 784965 times)

what claymore "scare" are you talking about?

the only difference between 2.7c and 2.7b was the addition of SSL. theres no reason NOT to use it vs the other versions

im talking about 2.7c... not pheonix in general

Because it’s faster and more stable than Claymore for a lot of people. Myself included.

And it has a lower fee. No brainer.

why use 2.7c?? it after claymore scare... not trust worthy cmon guys!

Thank you!

it works exactly like that, indexing for more than 10 gpu's are selected using letters (a,b,c...)


You're using the indexing feature of the miner, with -gpus 12 you're selecting to ONLY use gpu's One and Two, what you're looking for is to select the miner with the number OR letter if you have more than 10 (which seems to be your case)

"-gpus AB" for instance, will innitialize only your 11th and 12th gpu

I posted this a few pages back. It is still valid.

Using the -gt tuning can make a worthwhile increase in your hash rates.
This is only used for AMD cards.

Here is how I found the best way to tune and use it.

Have your miner up and running.
Using the '+' key increase the tuning parameter to a larger number than you need.
Start out at 100.
Watch your displayed hash rate in the mining window.
Let it display a few updates to see where the speed is currently running.
Decrease the tuning number by 10 using the '-' key.
Watch the hash rate.
Continue decreasing the number by 10 on each test while watching the hash rates.
You should see the hash rate starting to increase as you go down in numbers.
The hash rate will increase and then start to decrease.
When you reach that point you are close.
Now start going up and down by 5 instead of 10 on each test.
You will eventually find the sweet spot where you can't improve it any more.
Set that number in the -gt parameter in your config.txt file.

If you have multiple GPU's in a system you will need to do this for each GPU.
Disable all the GPU's but one. Find the best number for that GPU.
Record that number then disable that GPU and enable the next one.
Repeat until you have all the setting for each GPU.

This can take some time, but it’s worth it.

Thank you for the great tool.
Is it possible to specify SINGLE GPU above 9 ie 12?
-gpus 12 doesn't work
I have 15 cards and I want to do burn test of the particular 12 GPU.
Best regards,
CiN

Regarding the Debugger Error, I have a thing maybe. I discovered that when my troubled rig was installed, it was selected Windows 10 Pro *N* version. The same USB media installed to another rig (literally exact same hardware!) but just normal Pro, it works fine. Granted I have not swapped out the HDD and tested the error machine but it's literally the only difference I can manage to find.

Maybe it helps, maybe it's coincidence.

I have 8 AMD rigs, all works a better with clkernel 2 than 1, less the rigs with sapphire rx580 8gb, dont see any improvement compared to claymores

suggestion please

amd rx 460 2gb version - how about it? what is the parameter please. Thanks

Stable. but fans are loosing settings for AMD after some time and goes higher up to 95% fan speed then back, then up. I opened afterburner and use its fan setting - all is good when I use AB.

For the time being, the 2.7C is quite stable. So I will keep on using it.

So well my suggestion would be to revert back to claymore and forget about the whole phoenix miner thing until a new version comes out and works better.  See if your shares/payouts make sense, sometimes graphs can be stupid.

Dev, solo is here you da man!  BUT I do have a couple of comments:

1. Your example at the top of your 2.7c release says -coin Vic and Akroma, but down in the list you don't list either of those.  Can you please amend or tell us a full and accurate list of coins that work under the -coin feature please.

2. I am using drivers on my AMD cards that run like a bat out of hell speed wise on low DAG coins but once I go back to high DAG coins it goes to sheet.  But I only mine low DAG coins so it does not matter to me.  But an issue I ran into is that I have all along used -minspeed in clay to reset my miner and re-apply my OCs when they fail and whatnot, but because the dev DAG is high by default, the -minRigSpeed calculates the devfree speeds into its feature, thus, unless I mine a -coin I cannot use -minRigSpeed because the DAG lowers my MHS during the devfree periods and calls up my -r function.  Even though my own mining is at a nice and high tweaked speed.  Clay does not calculate the DevFree periods into the -minspeed totals.

3. I am switching to solo Vic now so will try the -coin Vic to avoid the DAG switching high and impacting the -minRigSpeed mis-calulations for a work around for now. (more of a statement).  My last coin was not available under the -coin feature thus I could not use the -minRigSpeed feature and had numerous OC drops were I went periods un-optimized by a card or two.

4. Am I wrong or is the capitalization for the command lines are required.  If it is spelled out as -minRigSpeed in the instructions then you have to use -minRigSpeed as -minrigspeed wont be recognized.  Seems kind of trivial and I am sure causing more folks then just myself a headache.  unless I am wrong and this was just a 4AM sleep issue.

I had this happen once last night and once today, latest released version 2.7c.

No, it is not the same issue.
This original hang was fix weeks ago.
Only happens when scrolling backwards.

Hello,


Every 24 hours or so I get this;

17596:15:34:21.877: GPU2 CUDA error in CudaProgram.cu:437 : the launch timed out and was terminated (702)
17596:15:34:21.933: GPU1 CUDART error in CudaProgram.cu:434 : the launch timed out and was terminated (6)
17596:15:34:21.972: GPU2 GPU2 search error: the launch timed out and was terminated
17596:15:34:21.972: GPU1 GPU1 search error: the launch timed out and was terminated


I'm assuming it's power draw or OC related (both are not aggressive so I'm assuming it must be the power limit), however from this can you deduce that GPU 2 is the culprit or is it too hard to tell?


Thanks!

any trouble? 2.7c was released after claymore scare, is virus or ?

difficulty should be static otherwise no of shares has no relevance in comparison.