Quote from: sea_of_blocks on March 21, 2021, 08:54:16 PM

Any chance we can load both DAG's for ETH and ZIL to the VRAM? Would love this feature on this miner... my favorite and for me the most stable.

Happy to contribute ($ETH) to the effort if this can get done... DM me.

Great work BTW!

Cheers!

No need to contribute. We will be adding this but it's not 100% sure that the feature will make it in this release - we will try our best.

Quote from: AnotherTreatment on March 21, 2021, 10:37:26 PM

Still wondering how many GBs do you need to use Kernel 3. Benching in a lower epoch, I'm getting 0.250 more MHs with Kernel 3 than 1....

You need exactly double the DAG size. We are working on updated -clkernel 3 kernels that will use whatever memory is available but the price is somewhat lower speed-up.

Quote from: iavelar on March 22, 2021, 01:25:54 AM

Hello guys.

receiving these errors in AMD 9 200 (GPU1) and RTX 3070 (GPU2) windows 10:

Quote

2021.03.21:22:11:43.771: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0)
2021.03.21:22:11:44.588: GPU1 Light cache generated in 4.7 s (14.1 MB/s)
2021.03.21:22:11:44.663: GPU1 GPU1: DAG size limited from 4239 MB to 4023 MB
2021.03.21:22:11:44.686: GPU1 GPU1: Free VRAM: 1.952 GB; used: 0.048 GB
2021.03.21:22:11:44.686: GPU1 GPU1: DAG size limited from 4239 MB to 4023 MB
2021.03.21:22:11:44.686: GPU1 GPU1: Disabling DAG pre-allocation (not enough VRAM)
2021.03.21:22:11:44.686: GPU1 GPU1: Allocating DAG for epoch #402 (3.93) GB
2021.03.21:22:11:44.686: GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
2021.03.21:22:11:44.686: wdog Fatal error detected. Restarting.

2021.03.21:22:11:47.194: GPU2 GPU2: Allocating DAG (4.16) GB; good for epoch up to #404
2021.03.21:22:11:47.322: GPU2 GPU2: Generating DAG for epoch #402
2021.03.21:22:11:47.510: GPU2 GPU2 initMiner error: Unable to initialize CUDA miner

any idea how to solve it?

The problem is the first card (AMD R9 200), which can't mine ETH anymore. Run the miner with -nvidia command-line argument to use only the second card.

Quote from: zorachus99 on March 22, 2021, 02:53:19 AM

Hi Guys,

So I've been doing some experimenting and have found some interesting stuff on the 1080ti and Phoenix Miner.

There is a magical realm at 60% powerlimit. In this realm, the Ethlargement Pill and reducing your memory clock will increase hashrate. I've tested other power limits and they do not act the same.

So with the following settings: 60% powerlimit, +160 core, -900mhz memory = 36.5Mh/s @ 140Watts

Without the Pill I get 25.5Mh/S.

Could easily get 44Mh/s at 80-90% power limit, but that is 200+ watts and hard on the old fans.

Does anyone have more optimal configs for Mh/Watt?

You can use -straps 2 instead of the pill. We run our 1080Ti with the following settings: -powlim -20 -mclock +756 -straps 2 -tt 63 -tmax 68 and they give 43-44 MH/s at 200W

Quote from: doncoyote on March 22, 2021, 06:14:04 PM

I just tried clKernel 3 and the result is this:

GPU1 The option -clKernel 3 is ignored for GPU1

Code:

2021.03.22:15:10:10.520: main Cmd line: -pool ssl://us1.ethermine.org:5555 -wal xxx -proto 3 -clkernel 3 -rmode 2 -mt 2 -mi 12
2021.03.22:15:10:10.520: main No CUDA driver found
2021.03.22:15:10:12.069: main OpenCL driver version: 21.1.1
2021.03.22:15:10:12.079: main Available GPUs for mining:
2021.03.22:15:10:12.079: main GPU1: AMD Radeon RX 6800 (pcie 3), OpenCL 2.0, 16 GB VRAM, 30 CUs
2021.03.22:15:10:18.984: GPU1 The option -clKernel 3 is ignored for GPU1
2021.03.22:15:10:19.574: GPU1 GPU1: Free VRAM: 15.922 GB; used: 0.063 GB

Any hints?

-clkernel 3 is only for Polaris GPUs - there is no speedup for the newer cards because of the architecture of the memory controller.

Quote from: swogerino on March 22, 2021, 09:36:29 PM

I am having problems with a RX 6800 XT, it gives me driver time out error after 30 minutes , 10 minutes, 2 days so it is random.I have 2 of these cards and one Nvidia RTX 3060 Ti and I am using this latest miner 5.5 from Phoenix.Is there any solution to this ?

PhoenixMiner 5.5c can't control clocks and fan speed on Radeon 6000 series GPUs properly. You need to use AMD control center to set the clocks and then do not use any of the miner options to set clocks, voltages, etc. This is already fixed in the new version, which will be released soon(ish).