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

Phoenixminer 5.1b is a problem at all, 3x rx 570 4gb keeps crashing, and hashrate normally 3016 now 2916 better even older versions phoenixminer, and why you can't mine nimiq with phoenixminer while using temredminer very stable eth and nimiq minen super..


https://github.com/todxx/teamredminer/releases


Happy mining :0

I have win 10 and 6x 1070 GPUs, and i using last PM version

Hasrate contanstly falling. Until today I using nvidia drivers 388.43 today I change (update) drivers to 442.59. Hasrate is still falling. My OC settings are
https://imgur.com/wj5jLir.png

Current PM settings:

PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal ETHaddress.rig01/[email protected] -epsw x -ftime 10 -rmode 2 -lidag 2 -wdog 1 -astats 1 -proto 2 -logsmaxsize 1

Does anyone have any idea why hasrate falling. Last 3 maybe 4 months I have avg. hasrate aournt 187 to 189 MH/s 6 months ago constantly 194.7 MH/s.

Tnx for all you answers and tips.

i tried to start miner today, and after initial lines of iniialising cards, after line generated light it just stop without any error both in CMD or in log.
6x580 4Gb cards and win10 with BETA version of drivers 17.x

any idea why miner just ends without any error/note/


regards

Since 21/07 morning got a issue with rx5700 look like it can't reduce core clock to setting, last night still fine.

Update: reflash again now I can reduce core speed to setting but speed reduce from 56.8 to 50.5 T_T

Hi Phoenix Miner DEVs

Epoch 350 is now the reported DAG on my miner.

Running 5.0e on Windows 10 with the latest updates, etc.,

Have been having issues, only noticed today (so I'm not sure how long it's been happening, or if you already know about the issue?).  The hash rate has dropped noticably, and there is an error running one of the commands.

----------------------------------

hardware:

x2 AMD Radeon RX470 8GB Mining Edition with the latest AMD Drivers 20.7.2
x1 AMD Radeon RX57000XT 8GB  with the latest AMD Drivers 20.7.2

----------------------------------

prior to Epoch 350:

RX470, 30.3 MH/s, consistent rate
RX5700XT, 54 MH/s, consistent rate

Total 114.6 MH/s

----------------------------------

since Epoch 350:

RX470, 29.3 MH/s, consistent rate
RX5700XT, 48 MH/s - 49.5 MH/s, variable rate

Total 106.6 MH/s - 108.1 MH/s, variable rate

(54 MH/s a bit low for an RX5700XT, but the GFX cards are all squashed in a desktop PC case and this card in particularly is being throttled by thermals, since I'm aware of this though, that's fine from my point of view until I pickup another case or open air mining frame)

----------------------------------

The AMD Radeon RX470 8GB Mining Edition, I was running the cards with the below argument, which worked prior to Epoch 350:

-clKernel 3

GPU1: clSetKernelArg (-49)
Fatal error detected. Restarting

----------------------------------

Running with the optimised setting prevents the fatal error:

-clKernel 1

----------------------------------

Since I was using the -clKernel 3 argument prior to Epoch 350 without an issue, and the argument produced the best/optimal hashrate for my RX470 GPUs and now there is an error and slightly lower overall hashrate, this indicates there is a bug somewhere, and I wanted to report.  I tested the same config on Phoenix 5.0b which had the same result. Other people may not report, and simply use other miners, and you'll lose their DEV FEEs as a result.

What error miner gives? Give screenshot.
Try to check by this way:
-ppf 65,65,65,65,65

Hi there!
I have problem today: after start Phoenix Miner 5.1b (and 5.0e before) miner was crash. This happened today about 05:00 (GMT +2) simultaneously on 2 rigs: they was work and suddenly crash:
https://piccy.info/view3/13906056/1e802ada36006862d3b9e01132e670d0/

I try restart miner, but this also crash:
https://piccy.info/view3/13906061/b236c788f5aef49139a7709d0616fc38/orig/
Crash happens after Light cache generated in as you see on the picture.

This same on the Phoenix Miner 5.1b and Phoenix Miner 5.0e. I dont do anything: rigs work and suddenly crash and now i cant run they.

Have you something idea about this?

v5.1b 

I see new version on HiveOS. What is the new features ?

I know whole thing, and a single command -ppf 65 working on whole rig from 5 cards but if i set it up as -ppf 65,66,67,65,65 then miner/rig don't working (don't working when have commas).
That's my problem

P.S. Sorry for my nervousness

It's not demagogic. Any parameter can be set like
-mclock 1250
for all devices or
-mclock 1250,0,1100 for each device individually. 1250 for 1st GPU, didn't change for 2nd GPU, 1100 for 3rd GPU etc.

Ask what you want to set for your devices and i can help you if you can't do that.

Can you help me specifically or just share demagogic advices?

Just read the theme.


The same way.

Hello.
Need some HELP about -ppf command.

How to set those command per GPUs because i have 5 GPUs and want to dedicate different -ppf value per each GPU?

TNX

(Cards are rx 570s and rx 580s)

I tweaked the timings using a third party software called AMD Memory Tweak you can find more information on this topic https://bitcointalksearch.org/topic/amd-mem-tweak-xl-readmodify-timingsppstraps-on-the-fly-5123724

it seems stable enough (I was able to init only with straps 0, and then switched to 5):




Also I tested on 1060 - the results are mixed. its 10*1060*6G, with this config:
-mclock +800,+800,+800,+775,+800,+775,+775,+800,+775,+800
-powlim -36,-36,-36,-36,-36,-36,-36,-36,-36,-36
-cclock +100,+100,+100,+100,+100,+100,+100,+100

straps 1 I can apply before the dag generation, and the speed goes from 234mh to about 240+ then 238 after few hours, then back to the initial 233-234. with other straps applied after the dag generation I can get better results, but the improvement seem to degrade with time... what gives?

Thank you Phoenix Miner! Unfortunately running it at admin level doesn't work either. I'll wait for next release

Hello everyone !

I have a rig with this error : "FATAL ERROR : Debugger Detected" just after the listing of the graphics cards.

Any idea why ?

RIG : 6x RX470 4GB, Windows 10 up to date, Adrenalin 20.2.2, PM 5.1b

I have the same error with previous miner version, same with ETH, ETC or Nicehash...

Thank you so much <3 You made my life easier.

Wow, thanks very much for the reply, @PhoenixMiner.  For clarification, this also occurred under Ubuntu 18.04.3 LTS (bionic).  The 18.04.3 build is on amdgpu-pro 19.50-967956 drivers.  For both builds (Ubuntu 18.04.3 and Ubuntu 20.04), rolling back to PhoenixMiner v5.0e resolved the issue.  Thanks very much for the heads-up that Ubuntu 20.04 is not supported, yet!  I'll keep investigating and let you know if I find anything else that might be useful.

    This is strange, as the -mt option works fine with most cards. We are going to implement more flexible straps for AMD cards soon (ideally - in the 5.2 version of PhoenixMiner) but in the meantime, you can try different drivers because the -mt option actually uses the straps from the driver.


    This could be related to the OS and driver versions. We haven't tested on Ubuntu 20.04 yet (our Linux test rigs use Ubuntu 16.x and Ubuntu 18.x) and it is possible that the new AMD pro drivers for 20.04 are different that these for 18.04 (this is certainly true for 20.20-1098277, which is released only for 20.04 and is not supported by PhoenixMiner yet). We are going to build some rigs with 20.04 soon but this will only be reflected in the next release of PhoenixMiner.


    First, you must run the miner as administrator in order to use the straps. It this doesn't help, we are also adding straps support for more Pascal-based cards for the next release (5.1c), which should be ready in a few days. As the number of different Pascal-based GPUs is too big to be able to obtain and test on all of the, we also added a new parameter in 5.1c that will allow you to "trick" PhoenixMiner that the card is supported even when it isn't, which should be useful for the more "exotic" GPU variants like Quadro, mining cards, etc.


   It tightens the memory timings of GDDR5 or GDDR5X chips of the Pascal-based Nvidia cards (GTX10x0), which may lead to better hashrate. If your card is supported it is definitely worth it to try this option. For some cards (these with GDDR5X memory) the results are quite good but even for GDDR5 cards there will be some improvement. Note that for some cards like 1070 (but not 1070Ti), which suffer from lower hashrate with each new epoch, you may need to allow more power by using higher power limit or higher core clock in order to see the improvement with the current high DAG epoch numbers on ETH and ETC.



   The way to specify different settings for each GPU is as follows:


   So, when the parameter is the same for all cards, just specify it once like thsi: -tt 67. When you want different values for each GPU, use it like this: -fanmin 50,75 - it this case the fanmin for the first card will be 50, for the second 75. Note that there must be no spaces between the comma and the numbers, and if you have more than two GPUs, you must specify a number for each of them.


    Yes, both -ttli and the Nvidia memory timing adjustments work under Linux too. You must run the program as root in order to use the straps.



     Not a bad idea but it may lead to instability. We will think about this for the next release. We are also exploring the possibility of adding KawPow support for the next release if time permits.