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

Ok. So there is no point using dual mine if u only have gpu?

Is correct to load two kernels?

GPU5: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)
GPU9: DAG 63% GPU3: DAG generated in 5.5 s (525.0 MB/s)
GPU3: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)
GPU2: DAG generated in 6.0 s (482.2 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)

I have entered only -clgreen kernel.

Verge, Shield, Neva, Info, Taj, Globaltoken and many more.

Google?

   The command line seems fine. As the crash happens after the mining has started perhaps the overclocking settings of the cards are too high. In the first few minutes the miner will perform auto-tune as there is not explicitly specified -gt parameter. You can try the following things to fix the problem:
  * Start the miner only with half GPUs (add -gpus 123456 to start with 6 GPUs only) and see if it still crashes. If not, wait until auto-tuning is over (it usually takes less than 5 minutes), press 's' on the miner console window and write down the -gt values (they should be fairly similar if the GPUs are the same). Then try to start the miner again with all GPUs but with added -gt parameter (e.g. -gt 45 if the best found -gt parameter was in 43-47 range for the individual GPUs).
  * Lower the memory clocks and/or increase the core voltage sligthly.
  * Try using the non-green kernels (remove -clgreen 1) or try using the alternative kernels (-clkernel 2)


   Thank you for reporting about the problem with the 'c' key. The message about switching to dual-mining mode is harmless but we fixed than anyway in 4.0b.
   -proto 3 works as before for us. Can you please send us a command-line example where it doesn't work?


   Can you please send us the log for the first 1-2 minutes? We are unable to reproduce this problem here.

The second beta of the new release is out. You can download PhoenixMiner 4.0b from here:

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes:

Here are the changes since 4.0a:
* Added support for the new Ubqhash algorithm required for mining UBQ. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ
* Some small bugfixes

Here are the changes since 3.5d:

* Implemented dual mining (Ethash/Blake2s) for some AMD GPUs (RX580/570/560/480/470/460 and Vega). Use the new -dpool, -dwal, -dpass, -dworker, and -dcoin options to set the Blake2s pool. You can set the secondary coin mining intensity with the -sci option. For more information see the Readme.txt file. Note that the devfee when using dual mining is 0.9% on the ethash coin (there is no devfee on the secondary coin).
* New kernels for most AMD GPUs with better performance and hashrate stability (you may need to run auto-tune again to find the best GT values)
* New kernels for Nvidia GPUs with slightly better hashrate
* Stability improvements in the Linux version
* Support for the latest Windows drivers for AMD GPUs (up to 18.11.2)
* Many other small fixes and improvements



Here is an example command-line to use dual-mining:
* ETH on ethermine.org ETH, Blake2s on Nicehash:
* Nicehash (Ethash + Blake2s):

Here are examples to use for UBQ mining:
* maxhash.org (UBIQ):
* ubiq.minerpool.net (UBIQ):
* ubiqpool.io (UBIQ):

Here are some notes on the 4.0 release (repeated from our post for 4.0a as they are relevant to 4.0b too):

• The best -sci values may be found via auto-tuning similar to the best -gt values in the ethash-only mode. You can either press "z" in the miner's console when dual-mining, or specify -sci 0 at the command line to force auto tune in dual-mining mode. Note that the auto-tune will find the best -sci value with respect to the speed of the ethash algorithm, even if the speed of the Blake2s becomes too low as a result of that.
• We got a lot of requests for Ubqhash support and we are in the process of implementing it. However it seems that some of the pools are still a little buggy. The ubqhash support should be ready in a few days.
• Unfortunately, the hardware control improvements weren't ready for this release. 4.0a still only supports controlling the clocks/fans/temperatures only on AMD GPUs under Windows. We will try to finish the changes for the final 4.0 release in about two weeks but the improvements in the kernels were deemed more important. There is no change in the hardware control for Linux too - you still have to use third party application for this
• The dual mining for the rest of AMD cards, and for Nvidia cards in currently being implemented.
• Finally, please note that the versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. Currently ETC is on DAG 233, so in less than two weeks the old version of PhoenixMiner won't be able to create DAG or mine ETC - you have to upgrade to PhoenixMiner 4.0. For ETH there is more time as it is on DAG 225, and it won't be affected until the next year. As with ETC, you just need to upgrade to the latest version of PhoenixMiner in order to fix the problem.
  

Verge (XVG) uses PoW consensus algorithm with hash functions Scrypt, x17, Groestl, Blake2s и lyra2rev2. As I know PhoenixMiner doesn't support it, but it is one of the best miners for Ethash algo. I'm using it on almost all rigs. There are some problems only with GTX1080 with Enlargment pill and on rig with ASRock H110 BTC with 12 AMD cards - they are crashing with Phoenix.

What is Blake2s? I cant find any coins on whattomine.com

Glad to hear support for UBQ HASH! You and your team is awesome! A Phoenix rising from the ashes of ETH!

-proto 3  does not work with 4. starts with default proto setting.
alsos if press c on miner screen(reload config), it starts miner in dual mining mode. i haven't set up dual miner.

My config:
-pool pool.minerall.io:3401 -pool2 pool.minerall.io:3401
-wal @@@@.Rig2
-proto 4
-coin eth
-tt 61,61,61,61,61,1,61,60,61
-tstop 70
-clgreen 1,1,1,1,0,1,1,0,1
-log 0
-mi 14
-retrydelay 0
-lidag 1
-amd

try this but without -mi and -proto 4(nicehash protocol), -mi command with high value can crash your rig, its only for rigs with stable work. -lidag will can help you solve this problem, try different numbers 1-3.

I'm using HIVE OS 0.6 now, all my AMD cards works like charm with Phoenix miner, but none of my Nvidia cards work with Phoenix Miner,

I tried parameters like:
-nvidia
-gser
-nvNew
-nvf
-coin

for sure I added 0 or 1 or value after them, but nothing works, cards can be initialized but no DAG log shows, hash rate stay at 0, nothing happened until miner restarted.

This is my first time to use your miner after reading all the comments here, they got my interest in using your it, by the way is my command line is correct? I am using 12 rx 570 4gb in 1 rig.. with win10 18.6.1 radeon, all cards are moded.

here's my command:

PhoenixMiner.exe -pool mine.house:7007 -wal 0x3d046******** -pass x -clgreen 1 -fanmin 45 -fanmax 70 -worker ** -coin dbix -stales 0 -cdm 0 -amd -acm

All of your help will be appreciated..

Thanks      

Result:

My rig crash every 3-5 mins running.

Rig with rx580 3.5d 388.500 - 4.0a 390.200mh and better stability(incorrect share) than 3.5 version.

I used 4.0 since you published it on two rigs

After auto-tune the value completely change 11 to 67 for RX580 and 11 to 37 for RX470.

Now the hasrate is very stable I don't have little drop of 1 Mh/s randomly nom the hasrate for my 4 RX580 is always 125,77x Mh/s not 125,6xx or 124,xxx, very impressive it's was the only concerned VS Claymore. same behavior with my 4 RX470.

I just remark that the first GPU have still a lower hasrate but with this version the gap increave even more, it's still ok.

And finally the global hasrate of the RIG increase a little bit 125,5xx Mh/s to 125,7xx Mhs for 4 RX580 and 119,4xx Mhs to 119,6xx for 4 RX470.

Great version !

 

PhoenixMiner 4.0a (Windows/Linux) added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

Got it, thank you for those details.

   Your cards are recognized but twice (the first two are your RX480 - it is listed as RX470 because of the video BIOS giving wrong device name string but it has 36 computing units, so it is the RX480). The reason is that the previous version of the drivers weren't completely removed before installing the new one. You should always remove the previous version of the drivers with DDU before installing the new ones. However, for the time being you can just add -gpus 13 to your command line to ignore the "twins" of your GPUs.

    This should fix the problem and leave only two cards. If you have -gt in your command line, remove it and after starting the miner wait for a few minutes before the auto-tune finds the best GT values. During the auto-tune you will initially see low hashrate but then it will go up.



  There is no need to change any settings, the new kernels replace the old ones. The difference is small but noticeable, especially with 1060 and 1050 cards. With 1080 and 1080Ti there is not much difference. With 9 series GPUs it is a bit of hit or miss but at least they aren't slower than the old kernels. It shouldn't matter which drivers you are using.

   When comparing make sure to compare with roughly the same DAG epoch (i.e. compare with the result for the same coin, instead of comparing ETC with ETH hashrate) because there is small but noticeable slowdown of even the 10 series Nvidia GPUs with each new DAG epoch. Hopefully Nvidia would fix it in the drivers as AMD did but given that this wasn't fixed for the 9th series, we aren't too hopeful. Thankfully, it is quite small.

What auto-tune ? The miner shows 4 cards, and all 470e when physically connected 2!!!!! One 470 and one 480

Hi there,

How to use/activate those new kernels?
Do they are auto activated by default or do we have to type some addition command line option to activate them?

And for which models are affected? 10 series? older? any Nvidia GPUs?
Do they need specified driver version too for optimal performance,
or at least some driver version and above, say 4xx.xx and above?

Thanks

PhoenixMiner
I have 2 GPUs on a RIG. One - RX470, One RX480. Drivers 18.11.1
Miner says:
2018.11.27:13:12:49.984: main GPU1: Radeon (TM) RX 470 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.11.27:13:12:49.984: main GPU2: Radeon (TM) RX 470 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.11.27:13:12:49.984: main GPU3: Radeon (TM) RX 470 Graphics (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.11.27:13:12:49.984: main GPU4: Radeon (TM) RX 470 Graphics (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs

Mining Speed low... 11Mh per card...