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

 
   One of the problems we found with the latest HiveOS can be fixed by removing the LD_PRELOAD environment variable. To do so, please insert the HiveOS USB flash drive with the already setup as a custom miner and  started at least once PhoenixMiner 3.5d on a PC and open the following folder in Windows explorer: /hive/custom/phoenixminer/. There you will find a file named h-run.sh. Open it with Notepad and add the following line unset LD_PRELOAD immediately before above the command that starts PhoenixMiner:


  If you are Linux-savvy, you can do this while HiveOS is running fron an SSH session and edit the file directly with the nano text editor.



  It just a coincidence that currently VIC and CLO are on the same DAG epoch. Note that the -coin parameter works only for the pools specified on the command-line (with the -pool and -pool2 command line parameters). If you have specified failover pools in the epools.txt file, you have to specify the coin for each pool in the list with , COIN: clo appended in the end of the pool line. If the coin isn't explicitly specified for one of the pools, PhoenixMiner tries to guess it from the DAG epoch but when two or more coins are currently in the same DAG epoch, it may guess wrong.
  However, this won't have any negative effect because when the DAG epochs are the same, there will be no DAG generation before or after the devfee periods anyway.

   We are investigating similar issue on Linux, but this is the first report that we get for similar behavior on Windows. We will try to reproduce it here and fix it.



  Please try using the -gser 1 option, or turn off the watchdog with -wdog 0 and see if this fixes the problem. We will make changes in the next release but it is important to know what is happening to avoid the problem in the future.


  About 90% probability that in the next version (3.6), there will be support for Blake2s.



   ProgPOW is certainly in our plans, and we will definitely add support one way or the other. Even if ETH drags its feet, we expect ETC or some other ethash-based coin to step up and support the network decentralization and security by adopting ProgPOW.

Hello PhoenixMiner!

Can you please tell me when it is planned to launch a dual mining (if planned)? If so, which algorithms are considered first? If you can, wish, then I would like to Blake2s

In advance I thank for answers!

we might have a winner here, switched over a bunch of rigs unstable undr claymore and the run greaat under your new kernal.  The powersavings is legit too 1 to 2% per rig
 also got better stability and constant hash rate on my furys too!!

this is your best release phoniex team , i have 300 amd card im switching over as we speak

any cance you can create a progpow miner , i suspect eth will be switching ovee some time next year

On HiveOS as well, was getting the same problem, and then I tried -gser 2, and that was able to initialize the first 5 cards until the miner detected that my other 3 cards (all NVIDIA 1060 3gb) was unresponsive and it restarted the miner again, then it just keeps going in that loop of creating the DAG for 5 cards and restarting the miner.  Is there a way to delay the miner from checking the cards until the -gser 2 has a chance to create the DAG for all the cards?

EDIT:  I also want to add that the current HiveOS startup for claymore can load the DAG for all 8 cards all at once.

eagerly awaiting the linux build with full nvidia clock and power limit control.

once that happens i'll switch my system to ubuntu 18.04

At the same time, on different machines, the miner hangs on generating a light cache for the epoch. ver.3.5d
https://screenshotscdn.firefoxusercontent.com/images/b65881b1-d7be-4eee-8478-039d6bd039a1.png
https://screenshotscdn.firefoxusercontent.com/images/91a6bc53-4d67-4331-bf26-53be58508029.png

It seems the latest version (3.5d) has problem with '-coin' param. I have specified '-coin clo' (or any coin) but at first it shows "Mining CLO on..." and later it shows "Mining VIC on..." VIC is dev's favorite coin? 

Not able to run on GeForce GTX 1060 6GB × 12

Running HiveOS 0.5-76   Nvidia Drivers : 390.59, is working perfectly fine on Ethminer and Claymore....

PhoenixMiner starts but mining does not start keeps on 0

Thanks.

Could you also try to fix problem with AMD cards? All of them are not detected by PhoenixMiner in HiveOS based on Ubuntu 18.04:


This build is named "Bleeding edge" =) https://hiveos.farm/install

   Thank you for the additional info - your CPU is definitely fine and way above the required minimum for timely generation of the light cache. We have since received another similar report on the same version on HiveOS, so we will investigate further and fix the problem when we found what is causing it.

the rig itself isnt bad it works fine with every miner , dont know where the problem is ..

That is a good save on power consumption! I too agree that PhoenixMiner is holding it down for the best ethereum miner.

   For Windows and AMD - anything from this year (18.x.x), including the latest 18.9.1. For Linux and AMD - 17.40 or above (18.10 if using Vega). For Nvidia - the latest driver should be OK. However for most of the old cards there are no new optimizations in the latest drivers and sometimes there are problems so if you are happy with your current drivers don't change them - usually the performance difference between the driver versions is very small.



  We will try to include support for it in the next release of PhoenixMiner.


   It seems that the light cache generation never finishes (as evidenced by the high CPU load too). It must finish in less than 10 seconds and then the card will create the DAGs but this never happens. This is not caused by the driver version for sure. We will try with this version of hiveOS but if it is based on Ubuntu 18.04, this also doesn't explain it because we have successfully tested with Ubuntu 18.04 as well. Can you please tell us what CPU do you have in this mining rig? Even the decade-old Athlon II should generate the light cache in less than 15 seconds.



   Yes, we have found this problem in the previous version (sometimes it crashes if a remote manager API requests are send before the miner is fully up and running), and therefore in the new version (3.5d) we have delayed the opening of the listening socket until the miner is ready to respond. So in the latest version (3.5d) it just won't respond to API requests in the first 15-25 seconds. However if you have these reports with the new version, please let us not and we will see what could be causing this. We tried to reproduce this with the new version but it doesn't crash as the old one.




    Well, this is definitely nice to hear! We are working on the next version, the first beta of which should be released in a few weeks.

Thank you for a new version with a new kernel mode for amd cards added . It allows me to decrease power consumption of my 7*rx570 rig by 12-14 watts  ,which is ~1,5% with the same hashrate ! Great job , I think Phoenix miner is and industry leading eth miner right now .

I haven't any problems in the past with phoenix, 3.5d same rock solid 24/7, nvidia rigs, waiting for HW control in 3.6 

@PhoenixMiner: I've been getting a number of reports on that PhoenixMiner crashes when launched from Awesome Miner, and it looks like the fact that Awesome Miner starts to make API calls early on is the issue here.

Once the Phoenix Miner is up and running with the mining, the API requests are processed by Phoenix Miner in a stable way, but sometimes when the API requests are processed during the first 20 seconds - the Phoenix Miner process crashes. Is it a known issue that making API calls to Phoenix Miner during the initialization phase can cause these crashes?

Many thanks!

I have latest hive os 5-75 - nvidia gtx 1060 cards 3gb memory / 396.54 driver , tried also 390.59 (downgraded it to test) , ubuntu 18.04 (I believe you can see latest hive os details log)



cards just dont do anything , cpu usage goes high.. any ideas ?
here is log file:

What driver version you can suggest for Nvidia cards?

can you add ROL coin for direct mining https://roller.today/

I've been using 18.3.4. drivers for AMD polaris cards and it have been stable for months.
I haven't had any problems with this version unlike beta blockchain drivers.