That double-point " :  " indicates that it somehow did not read --pool and --port correctly. Can you send me your settings in private msg, I will have a look whats going on (check them here at mine)


After replacement what kind of error msg you get?

Yes exactly - may be a little confusing, but Hive mainline still has the old lolMiner 0.34 (MinexCoin only) in, while lolMiner 0.5 is avail as a custom miner. As far as I know for Hive 6 this is to be changed. I hope to get my own 0.6 ready before so we do not have this mixing problem again

Hi there, as far as I know BZE is a fork of BitcoinZ with same mining settings, so you can use --coin BTCZ for this one



At the moment this does not work yet, since this is an other flavor of Equihash (200/9) - I do not know if I will add this, because there are already lots of asics around for this, so that is undecided yet. Maybe will do so for the sake of completeness.


Depends on the algorithms, what do you want to mine? (Since there are 4 different algorithms in this miner there is no single answer). Since you speak of kilosol/s it may be MNX - in 0.5 that should do ~10k sol/s, for 0.6 not yet known (still in development).

At the moment there is no (publicly available) ASIC for BTG yet. It switched in July to Equihash 144/5 which uses more memory then the older Equihash 200/9 from ZCash and currently there are no ASICs for the new algorithm variant to buy yet.

Best way to mine it is on GPU with one of the many CUDA miners like ewbf (this thread), funakoshi, bminer (etc...) or OpenCL based miner (lolMiner).

At the top of the log it should tell you about "using device ..." with the gpu name
It can be systematic that gpu2 has a flaw but also could be a problem in my code. If this happens multiple times an every time its a different GPU its likely to be a code problem, else a GPU one. Since this code is very new I would rather bet on code problem atm

You can enable --logs 1 and the miner will write all its text output to a logfile in ./logs directiory. Will be interesting of thus is a 0 sol/s or something like that - such things are hard to find in testing and thus exactly what I had hoped to discover with the public alpha

Hi there, I guess what happened is that the start script (run_miner.bat or run_miner.sh) is pointing to EXAMPLE_BTG, while your old pointed to BTCZ.
Overall 0.6 and 0.5 use same command line format and same config file style, so usually its just copying over the config and start scripts and run as used to before

Regarding stability: except for API and mining code the two versions are very similar. I expect alpha 1 to be similar stable / unstable as 0.5. Should work fine up to 4-5 GPUs while 5-6+ one better runs two copies of the miner. Only thing may be flaws in the new mining code. The AMD one just got ready yesterday while the Nvidia was now in testing for approx a week - I did not notice crashes or too many bad shares till now, but only have a bit limited test sys.



Wow, the R390 really kick ass - did not expect this. For the polaris GPUs the miner is now in bandwidth limit while was in clock limit before. Seems this helped more on older cards ^^

Regarding the Nvidias: Fit well to what I measured on my 1080s
But to be realistig you run quite high power target - afaik lolMiner likes that a bit more then ewbf 0.6 - with more moderate settings they should run equaly fast for 1080ti



Ah, well good aspect. I will try to change the hive integration over weekend so the alpha does not overwrite the 0.5 stable and one can insrall them side by side. Thx for reply, stay tuned

Thx for feedback
By the way: are you using the hive version? I modded the existing one for 0.5 for 0.6, but had no chance to test it. So would be great to know if its working (If I remember correctly you asked about Hove some time ago )

Hey Folks,

I just made the link to the first lolMiner 0.6 alpha release public.
You can find the new version here:

Readme: https://github.com/Lolliedieb/lolMiner-preview/blob/master/README.md
Release: https://github.com/Lolliedieb/lolMiner-preview/releases

Changes to 0.5 version:
- All algorithms removed except Equihash 144/5
- Faster mining on 144/5 compared to 0.5 stable release
- 0.6 uses now only 1850 MB of GPU memory and thus works on 2G cards
- Initial tuning for Nvidia RTX 2000 series
- Improved API


Details about the new API:
lolMiner 0.6 comes now with full http headers for the API, so the mime type is correct. As far as
I know now all common browsers can show the API output correctly. This also helps getting the
API output with tools like curl or any mining watchdog.

To call the api you now need the address /summary, e.g. localhost:8080/summary if your API port
was 8080. The preview version is not yet implementing the new 0.6 API in full (but the subset send
will not change in format). Next days I will put a list online with all the planned changes.

Note:
under /summary_trim you can find a API output where all white spaces and line-breaks are removed.
May help for some tools.

Speed estimates in new version (Equihash 144/5 only):
AMD:
RX 580: 27-29 sol/s
RX 560: 14 sol/s

Nvidia:
GTX 1080: 53-56 sol/s
GTX 1070: 40-45 sol/s
GTX 1060: 26-30 sol/s
more values to be added when available

Some results from tuning experiments:
AMD:
Clock is not so important here, memory bandwidth seems to be the key.
Tested setting was: 1200 / 1850 with -0.1v core and -20% power target

Nvidia:
lolMiner scales better with available compute power then most competitors.
(For example I saw it usually faster then ewbf for 1080 but slightly slower on
1070 cards, because the balance of compute power and memory bandwidth
is different between the two cards. )

Try to undervolt to get less energy consumption, but try to find settings
so that clocks do not drop too sharp. Setting a low power target without
undervolt may kill the performance.
Setting for the 1080 above were founders edition stocks. 1070 was tested at
70% PT and at stock clocks. 70% PT without undervolt gave 42 sol/s, stock
clocks 45 sol/s.

Whats coming next:
In the next versions I want to extend the API and implement a new work scheduler
which hopefully fixes the problems with more then 5 GPUs and reduces CPU load.
*Crossing fingers*
Also I want to apply the algorithm changes to the other algorithms as well and add
them successively to the alpha version

Usually the run_miner_with_restart.bat file should do exactly what you requested - unless it does not work as it should.  Can not check this because need a crash for this 

Hey guys, imao it is time for a



So, whats going on:

1. I just updated both file archives (Bugfix)

The bug making problems with ZEL, ANON and others is fixed. The updated binaries are in the links on the start side post. So, from now you again can just use --coin ZEL and so on for mining. Sorry for the problems you had with this.


2. We are on HIVE OS
lolMiner was recently added as a custom miner to HIVE OS. See here for loading the package:

https://forum.hiveos.farm/t/custom-miner-lolminer/8135

Configuration notice:
The default is "COIN" : "BTG" and "DEVICES" : "AMD" in the package. To mine any other coin you must add "COIN" : "<yourCoinShortCut>" to the "Extra Config Arguments" field. Overall this field uses the same style as the config file (Json). Please do not use --parameter VALUE there. This will likely make the miner just not run

Note: I already forwarded the bugfix from first news point to the Hive team. It should be updated there as well soon.


3. lolMiner 0.6 Casting its First Shadows
Well it took me a while thinking about how I will do the next release. Last time doing a long coding phase and then release all at one bang was too problematic, because too many bugs remained uncovered during that process. But I also was not able to spend more time for testing, because of running out of personal time (I have to do other jobs beside, because currently lolMiner does not return me enough bugs to work on this exclusively).

So I decided to do it differently this time: 0.5 will remain the stable version for the next weeks. The same time I will put up a github with ready to use binaries for 0.6 alpha versions and use the git bug tracker for getting rid of bugs. The first version will have some changes in the API and already come with new 144/5 mining codes. The other codes will miss in first version.
Next I will then implement the new mining main loop that hopefully reduces CPU demand and fix problems with >5 GPUs and then I will successively add the other mining codes. I think it is a good idea to do so, because this way those who want to profit from first changes can do early but help me to get bugs out for all others later.

Release of first alpha snapshot will be later this week.



-------------------
And now answering your questions:


See manual. --pers is the wrong option in lolMiner But also you just can update to the bugfix release and switch back to --coin ZEL




Great to see the improvements worked - hope we can add an other few sol/s on top soon

I just heard of this - all I can tell so far is that you are not the only ones, but seems only to happen on 144/5 algo. What works (atm) is use Auto144_5 profile and custom personalization string (see manual) ... I will see why this happens and try to come up with a solution asap.

No need to quote all the announcement ^^

Well lets start. On the 1st screenshot I see you use the wrong (old) command line format with -parameter=<someThing> ... it should be

As for the 2nd screen I have to admit I do not know why this happens. But from first guess: The 940M could just return its done to slow here - just from numbers it will likely only do 1-2 sol/s and therefore I think the GPU scheduler detects it as stuck because it does not report enough sol/s to my stuck detection mechanism. To be honest I would not mine with a 64 bit DDR3 mem bus + mobile GPU. Not worth the energy for keeping the notebook on all the time.

lolMiner just polls the OpenCL driver and asks for what cards are there and ready 2 run at the moment, nothing more. Its not an own routine, it just uses OpenCL standard functions. That said: I have seen this on my dev rig some time ago too. In the end it turned out to be a riser that somehow did not want as I did. But hard to say what causing this at your side.


Generally yes, but performance will be rather poor. Also only MNX and Aion will work because of only 1G of memory. So ... I have to admit I can not recommend doing so because unless you have free electricity the sol/s this old card (was low end in 2012!) will not justify turning your computer on for the time your mining.


By the way heavily working on 0.6 ... will take a while till its all done. But hope it will be great

Only thing I can see here is that the final closing bracket "}" is missing in your config file. Else I am able to mine with that config file as you can see right now in your dashboard (4x 580).
Setup time indeed takes a while (this is time to set up the GPU code for all GPUs and to establish the fee connection in background), especially on AMD (the compiler needs longer to compile there), but usually it should mine.

If your problems persist after adding "}", then can you try running
from command line to see if it is hashing at all? If yes it is likely some connection attempt of your miner gets blocked so it does not get pass the initial connection phase.



First of all thanks
I will have a look into that. Usually my back-end gets more and more flexible recently (i.e. AION needed a different stratum protocol, so I am now able to handle this). But I have to admit that new algorithms are currently not top priority - rather working on making the existing faster and the back-end more stable on multi GPU and less CPU time consuming. Hope to come along with first news regarding that soon

You are sure the hashrate is real also at the pool? Because I see an rejected share in the log. There is one routine in the code at the end that usually should sort out the invalid ones, but this seems to be broken at yours - interestingly only for the one card. I think the card is in fact hashing similar to the others, but produces ~50% defect shares :/
No idea yet why (I have not used ROCm driver much till now), but well - glad to see the driver working at all



Just now working on this. 0.6 will get a new host side mining engine that will hopefully handle things better More details to come



Generally lolMiner likes both, mem clock and core clock. So the best way I guess is to reduce core voltage and power limit to increase the efficiency. Overall I would try:
- leave core somewhere between 1200 and 1350
- memory up a bit - test whats stable
- power limit -20% and core voltage -0.1
This is likely a good start. Most ethereum settings with core clock at 1G or lower and high undervolt will likely end up in a crash or horrible performance here.

Glad to hear its working now

To add some points to the current technical discussion:
Yes, Equihash profits more from higher core clock then Ethash does. The reason is Ethash almost only does memory operations - loading stuff from memory, do small stuff and store back. So here memory bandwidth is crucial only. For Equihash this is different. The first phase of the algorithm is Blake2B, which is very compute heavy - this is approx 1/5th of the computation time (For 144/5 and 192/7 - for 210/9 it is a little less then this). Also my implementation uses in the later phases the shared memory a lot which works at core clock. So here the bandwidth also scales often with the clock.

So a general tuning advice of me would be to use clock near stock and memory can be upped a bit (lolMiner profits from fast memory, but not so much as Ethereum mining). Instead one can safely lower  the power target, because most rounds either use high clock or fast mem, but often not at the same time. Also what helps a lot to optimize performance over watts is undervolting. This helps in two ways: undervolted core use less energy. But this also means if you set a lower power target this means that its less likely the undervolted core has to throttle clock to stay within power target. Overall I would go for 1200 - 1350 clock + undervolt.


Without a question: Vega cards could do better. I will continue working on this!
But I think you underestimate here what monsters this Fury cards were Just to put some numbers:

Vega 64:
#Cores: 4096
Core Clock: 1247 / 1548
Memory: 8GB HBM 2, 483 GB/s

Fury X:
#Cores: 4096
Core Clock: ? / 1050
Memory: 4GB HBM, 512 GB/s

So you see ... the Vega clocks higher, but Fury even has more bandwidth. Vega had a lot of improvements regarding power management and so on and also some new compute features. But Equihash just do not need this. The operations done are almost all (64 bit) integer magic, memory operations, atomic operations and vector xor of integers. All the improvements in new features are almost unused. This is why lolMiner uses in fact OpenCL 1.2 and would still run on an ages old HD 5xxx series if it has enough memory. What makes Nvidia strong on Equihash is their cache line size, so some small detail in memory controller that is unchanged within AMD GCN series. By the way you see it here at the 96/5 and 144/5 algorithms. On Equi 144/5 it is hard for me to get an 580 close to a 1060. We are still approx 10 to 15% off. Here the Pascal architecture helps much.
On 96/5 instead this cards are on par. Why? Because 96/5's problem sizes allow to sort memory access better and so the disadvantage of cache line size vanishes.

So the only advantage of Vega over Fury is its higher clock (which is only useful in about 1/5 to 1/4th of the algorithm) and Vega does better sols/w. But overall it does not surprise me that Fury X can get close to Vega 56 at least.   


If your operation system allows using Nvidia and AMD mixed it will work. So you will need Windows or a custom Linux (most standard Linux do not allow AMD and NV drivers at the same time). But I will not guaranty for stability and speed. But - just to point an option - you can run the AMDs in lolMiner with --devices AMD (so only this cards are used) and open a 2nd command line with EWBF on the Nvidia cards. This constellation will give you most likely best performance.

I just updated the links in the front page.

The updated version resolved the password bug in command line

Yes. Zero did a fork to change some stuff, e.g. devs now get a small share of coin to push the development and for promoting it. Also it now has halving and thus a limited supply what was different before. Afaik one pool decided to stay on the old chain and thus created a new coin.



I just tested a bit around a with your settings.
So, this should be the content of your user_config.json:


And this should be the content of your run_miner.bat:


Put both in the directory where the lolMiner.exe is places.
Then just double click on the run_miner.bat and you should mine fine



Hi there, I checked and found indeed that there was a small bug!
I just updated the Linux download links to fix this. For Windows it will take approx 5-6 hours, because I am currently on the round with a Ubuntu Laptop only where I can not compile for Windows. I will give a notice when windows links are updated as well.

Thanks for reporting!


Ps:

For those who are interested in having their miner in their favorite Mining OS:
1) PIMP OS is currently testing their integration.
2) I had contact with SMOS. They will check if the miner is stable enough to include it
3) For Hive I am currently playing around with the custom miner integration. Looking good that this will work, so hope to present you the package here soon.

I will check this, usually it should work but will check and fix if not.


Can you give your full config file with code tag?

This part looking ok, but assume the only missing is a closing sign } at the end, then the last "," you showed us would be too much.
I can only debug full files


It works but results vary much depending on algo and your gpu, so you can test and mine with it, but I do not advertise it.



AUTO144 was renamed to AUTO144_5 as said in changelog / manual. But as pointed out before better use ANON now.