So, I did some more coding last week and so there is an update:
lolMiner 0.43 
Download Links:[Lin 64]:
Click me (0.43 for Linux) [Win 64]:
Click me (0.43 for Windows) here are the virustotal reports for the two executables:
Linux:
https://www.virustotal.com/#/file/dc2efb304b84ab92d1f085ecf61d1e470ce366f3801233072bead2809b0b3c9bWindows:
https://www.virustotal.com/#/file/1325784f9a9ff11bb077cc66937b66c28422d4e71dd46ae959ccad87d7799065Hint: As you can see the Microsoft Windows defender detects the mining software as "PUA:Win32/CoinMiner " (Surprise ... its mining coins
). So if you have trouble with it better replace the defender by any other anti virus (e.g. I use Avira AntiVir, which is also free) and you are fine.
Detailed Changelog:Added 192.7 Algorithm with coins Zero (ZER) and SafeCash (SCASH)lolMiner now supports the Equihash 192.7 algorithm. The two coins supported are Zero (ZER) and SafeCash (SCASH). At the moment the miner requires 3.7 GB GPU memory, so 3G cards are not supported. Nvidia 4G cards can mine with new “DISABLE_MEMCHECK” switch (see below).
There should not be a performance difference between 4G and 8G GPUs!
Expected performance:
AMD:
RX 550 (4 G): 3 sol/s (to be confirmed)
RX 560 (4 G): 5-6 sol/s
RX 570: 11-12 sol/s
RX 580: 12-13.5 sol/s
Vega 56: 18-20 sol/s
Nvidia:
GTX 1080 (stock FE): 20 sol/s+
GTX 1080ti: 30 sol/s+
Added support for zergpool Equihash 144.5 auto profit switching You can now connect to equihash144.mine.zergpool.com to use its auto coin switching / auto exchanging capacities. The needed setting is “COIN” : “AUTO144” or -coin=AUTO144
Added switch to disable memory checkUse “DISABLE_MEMCHECK” : 1 or -disable_memcheck=1 to turn of the miners compatility memory checking. This fixes a problem with the Nvidia driver not reporting enough memory for Equihash 144.5 (3G & 4G cards) and 192.7 (4G cards)
Note: Disabling the memory check also implies the miner can no longer check how large the workbatch is allowed to be, so DO NOT USE THIS WITH EQUIHASH 96.5 (MinexCoin) . It will kill your performance.
Fixed support for open source Linux driverslolMiner should now be able to start on the open source Linux drivers but the performance is very much untested. Also for 144.5 and 192.7 the memory check may need to be disabled.
Fixed a bug with miner not starting without config fileAs said, you now can delete the user_config.json and run completely without it by using the command line only. Note that the config file still has the advantage of storing your settings for multiple coins in one file as well as fail-over pool support. The filename and the used profile of config file can be changed by parameters (see manual).
Fixed a bug with miner not starting (hanging in setup)It now can take a minute or two for the fail-over routine to kick in, but this should fix the problem.
Shortened the target printing to the first 16 charactersPreviously printing 64, making the lines unnecessary long.
Added some colors (very subdued )Stratum messages of new job, new target and submitted / accepted shares are now print in a green tone and the long statistics in some not too bright cyan. If you see a red message thats a stratum error message or a case where the server responded {"id": 4, "result": false, "error": null}, which means a share got not accepted.
Know issues:Sometimes the 144.5 and 192.7 codes run into the 0 sol/s bug even without OC. I hope to get rid of that in the next code iteration.
For some Nvidia GPUs specifying “WORKBATCH” : “HIGH” in config file leads to 0 sol/s from start. From command line it works fine. Investigating why.
Question is now: What am I coding next for 0.5?Here I would like to have your feedback! There is one thing I will do any ways: I tried a new code variant with the 192.7 miner that is there applied in the first two rounds of code. It turns out that this works quite well and so I would like to bring this for 96.5, 144.5 and 192.7 for both vendors next. This also will likely reduce the memory consumption of 144.5 to 2.4 G and of 192.7 slightly below 3G, so the 3G cards are back on board for 192.7.
But after that? You may decide!
Here is a list about the potential list of what I could do for 0.5:- 210.9 (Aion) mining code
- 200.9 (Zcash, …) mining code
- A memory saving 144.5 variant (sub 2G, approx 10 – 15% slower then the large memory one)
- A memory saving 192.7 variant (sub 2G, approx 25 – 30% slower then the large memory one)
- An HTML version of the API (viewing)
- Coupling of multiple miners, so API of one rig can show stats of whole farm
- Re-Design of stats module & API, e.g. logfile output and so on … need some more ideas here, comments welcome!
Regarding the last point in list: I definitely will never change fan speed or clocks in the miner, because this is responsibility of the driver or external OC tools. But what I could try is temp readings and an emergency switch off at high temps or so … do not know.
As said the main priority lies in the updated mining codes. That will take a while. Therefore I would say everyone commenting here or sending me a message in either telegram or discord is allowed to state two things from the optional list. I will evaluate in two weeks (Sept 12) and then work the list from top to bottom
Have a nice day all
Can you try to run clinfo.exe (is shipped with the AMD driver) and paste me the output into a private message? The incompatibility message usually comes when some memory check fails. Lets see what clinfo reports, then I can tell you what is wrong. As a first guess: some drivers limit the amount of memory that can be allocated in a single memory buffer. For AMD it often helps to execute 
