Hmm depends - on Windows that can happen, on Linux I would say no!
Working heavily on lolMiner 1.12 to correct what happened in Windows ... my strategy to allocate memory was a bit too aggressive there and I seem to read / write locations I should not touch. Will be fixed soon
Help me, pls!
I use version 1.11 of Linux with driver 20.10.
R9 390 ETH - 16 MH.... V. 1.11
--algo=ETHASH --pool %POOL% --user %WALLET_TPL% --pass x
On other miners (Phoenix 5.1) -everything is fine, 30 MH.
What should I do or what am I doing wrong?
Do I need to add something to the command line for NiceHash?
With respect.
Hey there. I have to admit I was not able to do much work for the Hawaii cards yet. They work somehow, but seem slower then other miners. This has architecture reasons - every architecture reacts a bit different to the code and optimizations and R9 390 have GCN2, while e.g. R9 380 / R9 Fury and RX 470 - 590 are GCN 3. Thus it might happen that my codes for 380 are quicker then for 390. Once I sorted out other problems of the miner I will go back to scratchboard and see what I can do for the older architectures.
By the way if you wonder what I currently do:
lolMiner 1.12 will get ethash support for NV cards - not tuned to the max, but may be an option for mixed rigs. Also slightly improved the Fiji (Fury) & 470-590 kernels, addend support for the ETC dag size reduction that will happen from epoch 390 and working on fixing defect shares in Windows. Busy days
Hi i got some doubts:
1 -Have lolminer an failoverpool?
2- Have discord or telegram too?
3- We cant mix vega with rx580?
4- have an internal watchdog too?
Can t find the info on readme
Thanks