Is correct to load two kernels?
GPU5: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)
GPU9: DAG 63%
GPU3: DAG generated in 5.5 s (525.0 MB/s)
GPU3: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)
GPU2: DAG generated in 6.0 s (482.2 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clgreen 1)
I have entered only -clgreen kernel.
Yes, this is correct and there is no error. This is just a new way to show you the kind of kernel each GPU is using by showing the relevant command-line options for this GPU (as some GPUs don't support -clkernel 2, others don't support -clgreen 1 kernels, etc). In the versions before 4.0 it was shown as "optimized green kernel".
Having issues with UBQ-HASH and naming workers. If I put anything after my address example (a9224303048j9.RIG1) It will not connect to the pool (Ubiq.Hodlpool:8009). If I get rid of the rig name it will connect and hash fine (BTW 6-7Mh/s increase over UBQHASH ETHminer!)
Depending on the pool, you may have to use the
-worker command line option (or
WORKER: in the epools.txt). Some pools accept the worker name as part of the wallet but others require it to be separate.
On behalf of the MaxHash Pools team and our Ubiq community, we would like to personally thank the Phoenix miner devs for incorporating Ubiq miner into the latest build.
Great job on giving miners another option and if you need any assistance/advice on Ubiq related matters then feel free to get in touch.
Big props!
-Team MaxHash
Thank you! We are glad to support Ubqhash as something like this is probably the way forward in the battle against ASIC miners. Thankfully the ubqhash didn't require huge changes in our code base, so it was done relatively quickly.
...
- Finally, please note that the versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. Currently ETC is on DAG 233, so in less than two weeks the old version of PhoenixMiner won't be able to create DAG or mine ETC - you have to upgrade to PhoenixMiner 4.0. For ETH there is more time as it is on DAG 225, and it won't be affected until the next year. As with ETC, you just need to upgrade to the latest version of PhoenixMiner in order to fix the problem.
I tried the new beta version, and I still got the "CudaProgram.cu:407 : out of memory " with my 1060 3gb cards if I start ETC mining.
You have to use Windows 7 or Linux to mine ETC (and soon ETH) with 1060 3GB as Windows 10 "steals" part of the video RAM, making the allocation of enough memory for the DAG impossible even though the DAG is still way less than 3 GB.
How will dual mining affect ETH hashrate and power usage?
Using radeon 570
I try with my 4x RX470, 600 W in solo, 705 W adding Blake2S from Nicehash, the hasrate drop from 29,8 MH/s per card to 28,2 Mh/s
Does blake2s earnings cover the new power cost?
For the most miners - no. However some may have access to very cheap or free electricity, or want to mine other coins for whatever reasons (want to support the blockchain, believe in the potential of said coin, etc), so there are reasons for dual mining, just not for most miners.
Could You create dedicated thread in forum with first post always contain newer version od this miner?
or github?
...like other miners does already (t-rex, z-enemy...., and almost all others).
I wish to have easy way to automate check for new versions
We only put a new release in the first post whenever it is deemed stable enough for wide release. Before that it is in "open" beta stage where everyone can try it but it is not recommended for wide deployment for example on big farms with a lot of rigs.
