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

Increase the virtual memory of your system to at least 82 GB (13 X 2 X 3GB for the dags + 4GB for OS and apps) in order 4.1 to work.

Phoenix Miner has been added to the https://prominertools.com archive.

View all available versions of this miner at https://prominertools.com/phoenix-miner/

PM 4.1c with 13xAMD RX580-8GB Fails using turbo mode kernel (-clkernel 3)

Error - immediately following DAG load; always exactly the same error. Switch back to 4.0b works great.

019.01.16:09:06:46.114: GPU7 GPU7: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:46.355: GPU10 GPU10: DAG 100%
2019.01.16:09:06:46.480: GPU8 GPU8: DAG 100%
2019.01.16:09:06:47.111: GPU11 GPU11: DAG 100%
2019.01.16:09:06:47.154: GPU12 GPU12: DAG 100%
2019.01.16:09:06:47.160: GPU9 GPU9: DAG 100%
2019.01.16:09:06:47.410: main 
2019.01.16:09:06:47.410: main *** 0:00 *** 1/16 09:06 **************************************
2019.01.16:09:06:47.410: main Eth: Mining ETH on eu1.ethermine.org:4444 for 0:00
2019.01.16:09:06:47.410: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.01.16:09:06:47.410: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.01.16:09:06:47.410: main Eth: Average speed (5 min): 86.233 MH/s
2019.01.16:09:06:47.410: main 
2019.01.16:09:06:47.867: GPU12 GPU12: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:47.984: GPU11 GPU11: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:47.988: GPU8 GPU8: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:48.140: GPU10 GPU10: DAG generated in 39.1 s (74.3 MB/s)
2019.01.16:09:06:48.141: GPU10 GPU10: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:48.178: GPU9 GPU9: DAG generated in 39.6 s (73.4 MB/s)
2019.01.16:09:06:48.179: GPU9 GPU9: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:48.206: GPU13 GPU13: DAG 100%
2019.01.16:09:06:48.229: main Eth speed: 107.135 MH/s, shares: 0/0/0, time: 0:00
2019.01.16:09:06:48.229: main GPUs: 1: 28.986 MH/s (0) 2: 25.954 MH/s (0) 3: 0.000 MH/s (0) 4: 28.715 MH/s (0) 5: 23.481 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0) 9: 0.000 MH/s (0) 10: 0.000 MH/s (0) 11: 0.000 MH/s (0) 12: 0.000 MH/s (0) 13: 0.000 MH/s (0)
2019.01.16:09:06:48.277: wdog Thread(s) not responding. Restarting.
2019.01.16:09:06:48.409: GPU13 GPU13: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:49.658: eths Eth: New job #b21615c5 from eu1.ethermine.org:4444; diff: 4000MH
2019.01.16:09:06:49.673: GPU8 GPU8: Starting up... (0)
2019.01.16:09:06:49.686: GPU11 GPU11: Starting up... (0)
2019.01.16:09:06:49.706: GPU12 GPU12: Starting up... (0)
2019.01.16:09:06:49.711: GPU13 GPU13: Starting up... (0)
2019.01.16:09:06:49.752: GPU8 GPU8: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.752: GPU8 GPU8: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.832: GPU11 GPU11: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.832: GPU11 GPU11: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.909: GPU12 GPU12: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.909: GPU12 GPU12: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.974: GPU8 GPU8: Generating DAG for epoch #235
2019.01.16:09:06:49.982: GPU8 GPU8: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:49.995: GPU13 GPU13: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.995: GPU13 GPU13: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:50.053: GPU11 GPU11: Generating DAG for epoch #235
2019.01.16:09:06:50.068: GPU11 GPU11: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.130: GPU12 GPU12: Generating DAG for epoch #235
2019.01.16:09:06:50.145: GPU12 GPU12: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.215: GPU13 GPU13: Generating DAG for epoch #235
2019.01.16:09:06:50.230: GPU13 GPU13: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.927: eths Eth: New job #ba79b5f7 from eu1.ethermine.org:4444; diff: 4000MH
2019.01.16:09:06:50.941: GPU8 GPU8: Starting up... (0)
2019.01.16:09:06:50.945: GPU11 GPU11: Starting up... (0)
2019.01.16:09:06:50.964: GPU12 GPU12: Starting up... (0)
2019.01.16:09:06:50.967: GPU13 GPU13: Starting up... (0)
2019.01.16:09:06:51.015: GPU8 GPU8: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.015: GPU8 GPU8: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:51.093: GPU11 GPU11: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.093: GPU11 GPU11: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:51.175: GPU12 GPU12: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.175: GPU12 GPU12: Allocating light cache buffer (45.6) MB; good for epoch up to #237

On a second mixed rig 7+6 (nvidia/amd) seeing 0-0.3 MH/s hash rate increase. Tried -lidag 3, same results.

-mi

Default is 12, try lowering

I am struggling with mining and using applications that has hardware acceleration on the same computer, i have a 1080 ti card, and whenever i use phoenixminer and watching youtube, its very laggy, discord is laggy and tradingview.com is very laggy

is there a way or a parameter to set on phoenixminer so that it uses the lowest priority so other applications can get the full hw speed they require ?

...I think it have to be the AMD driver --- did also not work under claymore! Back to v18.11.1?

even with MSI AfterBurner !!!

With AMD driver version 18.12.2 and latest 4.1c version, it seems that the fan control did not work here (@RX470/480/570 cards).
Any problems known about this?

Hi

have there real problems, when mines with R9 390 u. R9 390X GPU's .....
For some months, the hashrate is decreasing continuously from formerly about 33 Mhs / s to about 25.9 Mhs / s even though the R9 390 (X) of the DAG Epoch problem should not be affected at all ...
have any idea to get back 33 Mh/s
Resiste the DAG Epoch

I can`t see if I can use -Kernel option per GPU. Is it impossible at all or it is miner limitation?
I have a rig with one RX580 8Gb and four RX570 4Gb and wanna try turbo kernels. Any suggestions?

   We have but it is not yet ready for the public releases.


   We have performed a quick test and there were no issues. Here is the command line we used:


   If the problems persists, please send us a (partial) log file to see what is going wrong.


   Supported AMD Linux drivers are 16.40, 16.60, 17.10, 17.20, 17.30, 17.40, 17.50, 18.10, 18.20, 18.30, 18.40. The latest 18.50 drivers are not supported yet.


   Set -mi 0. If this is not enough, try -mi 8 -gpow 80 or -mi 8 -li 1 Increase/decrease the -gpow or -li values until you have smooth desktop experience without losing too much hashrate.

The third beta of the new release is out (note that 4.1b wasn't released as we found some small bugs before it was out). You can download PhoenixMiner 4.1c 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.1a (the first beta of 4.1):

• Added support for turbo kernels (-clkernel 3) and dual mining
• Added command-line option -vs to just print the version (e.g. 4.1c) and exit
• Added command-line option -wdtimeout to set the timeout of the watchdog timer. The valid values are from 30 to 300 seconds, the default is 45 seconds.
• Added support for Windows AMD drivers 19.1.1
• Small bugfixes

Here are the changes since 4.0b (the previous stable release):

• Added faster "turbo" kernels (-clkernel 3) for AMD 470/480/570/580 GPUs. These are usually faster than normal kernels (-clkernel 1 or -clkernel 2) but require double the amount of VRAM. This means that you can only use them on 8 GB cards if mining ETH or ETC. You can use them on cards with 4 GB or less VRAM only if you are mining low DAG epoch coins.
• Added Blake2s dual mining kernels, and green kernels for AMD Fury GPUs
• Added Blake2s dual mining kernels for AMD 280/285/290/380/390 GPUs
• New faster kernels for AMD 280/290/390 GPUs
• Added alternative kernels (-clkernel 2) for AMD 280 GPUs
• Added options -pauseat and -resumeat for scheduled pausing and resuming of the miner. Example: -resumeat 22:00 -pauseat 6:00 - the miner will mine only between 22:00 and 6:00. Example 2: -resumeat 22:00,12:00 -pauseat 6:00,16:00 - you can specify multiple pause and resume times.
• (Windows only) The miner now prevents the computer from sleeping if the mining is not paused, and wakes the computer when it must resume mining at the time specified with -resumeat command-line option. In combination with -pauseat and -resumeat options this allows you to mine only when the electricity rates are lower and to keep your rig(s) asleep the rest of the time.
• When the miner is paused for more than a few minutes, the pool is disconnected. The pool connection is restored when the mining is resumed.
• Added a watchdog protection against freezing of the network connection thread
• Automatic selection of compatible devfee coin if there isn't enough VRAM to mine ETH and the main coin can't be recognized or isn't supported for devfee
• Automatic switch to the next pool if the cards VRAM is not enough for the requited DAG epoch. This is especially useful if the pool is auto-switching the coins but your cards only support lower DAG epoch coins.
• Added a -rvram option to set the minimal reserved VRAM that can't be used for mining. The default values are 384 MB on Windows, and 128 MB on Linux. You can also set -rvram -1 if you want to turn off the protection against using too much VRAM.
• Added support for Windows AMD drivers 18.12.x
• Other small improvements and fixes

Finally, please note that the versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. Currently ETC is above this, and ETH is going to be on epoch 236 very soon. If you want to continue to mine ETH and ETCH, you must upgrade to PhoenixMiner 4.x.

what config do you guys use when you're trying to avoid screen lag?
I noticed that -mi set to lower than the default does not seem to affect screen lag and hashrate

so I'm still wondering which config should I change in case i want to use the computer while the miner is still running
I have set -mi to 12 when I'm not doing anything other than mining

Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2766.4)
Available GPUs for mining:
GPU1: AMD Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 1.2, 3.2 GB VRAM, 36 CUs
GPU2: AMD Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 1.2, 7.9 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie , OpenCL 1.2, 8 GB VRAM, 36 CUs

im on ubuntu. i wonder witch is the know opencl driver ?

With Ethermine, my reported hasrate is a little bit better but the current hasrate is lower and so the average hashrate. I don't have anormal rejected/invalide/stale share.

Going back to the previous version and the current hashrate and average hasrate goes up.

whalesburg miners reported some troubles with new version, sometimes miner restart or stuck

Same problem here , i have 2 rigs on a pool , but reported hashrate is only from the 1 rig ... i will go back to the previous version of PM

User reported that 4.1a doesn't work with pool on etcget.net, but 4.0b was working fine. Could be same with other similar pools. Worth to inspect.

ONLY IN GAMING YOU WILL NOTICE DIFFERENCE ! In mining drivers are the SAME ! i had tested 12 kinds of version of amd drivers , all the same results !

Any chance you have a beta version with ProgPow already implemented for coins like Bitcoin Interest (BCI)?

https://github.com/BitcoinInterestOfficial/ProgPOW