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

   Depending on what secondary algorithm we do because we once (almost) implemented DCR and it went to non-profitable. It wasn't entirely lost effort but close to it. After finishing the Linux version we will reevaluate the most profitable choices for a secondary coin and then it would take additional month or so. So at least two months in the future.

  Yes. We check if the Compute mode is required by both for each GPU, and the driver. For example, if you are using the blockchain beta driver, the Compute mode is not needed because the huge page mode is already turned on in the driver.

  Usually it is good idea to put them in the .bat file (or in the config.txt file, if you are using it). In such case you will need to run auto-tune again if you change the clocks on any of the cards, if you install new version of the driver, or if you try using the alternative kernels (-clkernel 2), as the best -gt values could be very different for the two types of kernels. It is also good idea to check if the -gt values are still the best if you upgrade the GPU drivers or install a new version of PhoenixMiner in the future.

   However if you are restarting your rigs only once a week or so, you can just let auto-tune run at each startup as it takes only a few minutes.

   If you are getting the infamous 999 error, you need to lower the memory overclock by 10-20 MHz.



According to nanopool documentation, you have to specify the pool like this:

To specify that only the first 9 cards should be used by given PhoenixMiner instance, use -gpus 123456789. To specify the first 11 cards, use -gpus 1,2,3,4,5,6,7,8,9,10,11. The only important thing is to use commas (without spaces) to separate indexes if you are going to use 10 or more as an index of a GPU.


   The clocks are reset when the miner is closing to prevent crashes if you start something else that loads the GPU in different way and the voltage settings are not good enough. Ethash is notoriously tolerant to low core voltage but if you try to run any intensive game or more core-intensive mining algorithm, the GPUs will most probably crash if the settings are left unchanged. It is not that hard to add such option though, and we will add it in the next version, time permitting.

   As for the lower hashrate, please try running both the normal and alternative (-clkernel 2) kernels and run auto-tune with both to see the maximum obtainable hashrate.

   Hopefully in the next release.


   Sorry about this issue. To help us reproduce it and fix it, can you please tell us what -gser option you are using and with what cards/drivers/OS you are using?

   We will add option to avoid resetting OC on exit in the next version.

    You can use the -worker option too depending on the pool.

Hi PhoenixMiner

How long to wait for the version for dual mining?

hi support, i m using 6GPUs RX580 8G,  when i push "y" , why the system prompt the compute mode is not required, what does it meant? is it meant already fully optimize for these GPUS

After autotuning, should I just put the found values in the bat file, or could it change from run to run?

I was using -gt 15 for 3 cards (480, 570 and 580) and now autotune found -gt 13,18,16.

Error fan at 3.0s, how to arrange (1060 card 6g, driver 388.13)

First, thanks for creating such a great miner.
I don't get it how to make it mine ETC (ETH mining works perfectly). It submitted only a couple of shares to the pool. The rest is just not being submitted. I tried different types of deviding wal/workername/password, trough dot, slash etc. That doesn't seem to be the issue, since some shares were sent.
Can someone help please?
This is how my bat files looks. Another small question, how do I turn off the mining for cards 10+? Most of my rigs have less than that, but I have one rig with 13 gpu.

I noticed that when exiting, the cards clocks reset to default. I don't want that, is there any way to prevent it?

Also, 3.0 seems a bit slower that 2.9

With all setting equal (launching from bat file) 2.9 gives around 600h/s more with 3 ellesmere cards.

When do u wanna support Nvidia OC setting like Claymore ?

- Your -gser param is so magic! It makes my GPUs hang at start-up. Error msg: GPUx not responding!
- if not specify -gt param, my rigs often crash when it is auto-tuning.

Well I use Rx 470/570/480/580 cards.
Latest Amd drivers, never had crashing problems when closing the miner until v3.0C

Is there a way to name the rig besides putting it behind the wallet address?  My pool doesn't like that format...