Could you please add the resulting autotuning parameters to the API?
Thaaaaaaaaank you!
There will be substantial additions to the remote management API but not in this release.
Still no overclock or voltage control on nvidia cards?
Ethos has been able to do this for a long time.
We are giving priority to any ideas to bring up the ROI of the mining but these will be implemented eventually.
Please suppress the warning messages about invalid epools.txt when valid epool parameters are passed via command line.
Eth: Invalid wallet 'YourWallet.BLACKBOX' specified for pool 1 from epools.txt. Replace with a real wallet
Eth: Invalid wallet 'YourWallet.BLACKBOX' specified for pool 2 from epools.txt. Replace with a real wallet
# The pools specified in this file will be added to the pools specified with the PhoenixMiner's
# command-line options (see -pool and -pool2 command line options).
When -epool -or -dpool is present, then no other pools should be used.
This would change the way the miner behaved in all current releases, which will definitely cause problems for many users. You can either rename the epools.txt to something else, or comment out all lines there with the # character at the start of each line.
turbo kernel error clCreateKernel (-46):
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------
CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
^C
c:\Users\Stephan\Desktop\MultiPoolMiner-Test\Bin\AMD_NVIDIA-PhoenixminerEthash_v4.1a>PhoenixMiner.exe -mport -4004 -proto 1 -pool europe.ethash-hub.miningpoolhub.com:20565 -wal ***************** -pass x -dcoin blake2s -dpool blake2s.eu.nicehash.com:3361 -dwal *************************.multipoolminer -dpass x -sci 60 -gt 0 -log 0 -wdog 0 -clkernel 3 -gpus 3
Phoenix Miner 4.1a Windows/msvc - Release build
-----------------------------------------------
CUDA version: 10.0, CUDA runtime: 8.0
OpenCL driver version: 18.12.2,
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
...
Light cache generated in 0.9 s (26.0 MB/s)
GPU1: Allocating DAG (2x 1.44) GB; good for epoch up to #56
GPU1: Generating DAG for epoch #54
GPU1: DAG 50%
GPU1: DAG 100%
GPU1: DAG generated in 3.2 s (452.0 MB/s)
GPU1: Unable to prepare kernels: clCreateKernel (-46)
Card is a RX 570 4 GB model. Should this not be enough memory?
Thank you for reporting this. The -clkernel 3 option doesn't work with dual mining yet. We will try to include the turbo dual mining kernels in the final 4.1 release.
any plans for kernal 3 for fury x or vega 64?
also the setting of etth (claymore lower limti of 50 being lowered to 25?) i think can help squeeze out some more hashs..
thanks
Unfortunately the techniques that make -clkernel 3 faster doesn't work on Fury and Vega GPUs. Can you please clarify what do you mean by
etth?