Topic: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22) - page 36. (Read 30772 times)

I will difinetly try this one today, thanks Lolliedieb for you hardwork, really appreciate it!  

By the way, how about the speed? is it also increase it?

So, this time a minor update I guess, but it may improve the user experience.

Time for version 0.22  

Here are the download links:
Linux 64: Click me (v0.22)
Windows 64: Click me (v0.22)

Lets see what I have for you today:

Introduce the ability to use configuration files
Use "--use-config " to load your configuration from file instead of from command line. This also makes maintaining multiple copies of lolMiner easier. See the example file to see how these files are written.

Use "--enable-time-print" to perpend the current local time to the statistics output
Well do not have more for that, do I? Ok: if you enable this HH:MM:SS in your local system time is printed before the stats.

Enable v0.13 thread model by "--use-alt-mine-thread"
This will enable the work handling of lolMiner-mnx 0.13 but with all the other bug fixes and improvements still enabled. This will deactivate multi-gpu support, so only the first device listed in --device will be used. By default the Nvidia CPU load fix (hotfix) is enabled, see below how to disable this. This option will brings back support for Intel devices.

New expert switch "--set-sleep-duration "
This switch controls the new thread model introduced by 0.21.  It sets the time span between polling the GPUs for completed work in microseconds. Lower values may stabilize the performance, but also increase CPU load for all vendors. Setting the value to 0 will make lolMiner-mnx use one full CPU core by 100% for handling all devices. If this is used with "--use-alt-mine-thread" it will disable the Nvidia hotfix. Higher values reduce CPU load but may reduce hash rate. Default is 1000 microseconds = 1 millisecond.

[Windows] Hibernating is now prevented
lolMiner-mnx now reports Windows that it does not want Windows to switch to power save, hibernate and switching screen of automatically.

Improved thread safety
I inserted some mutex so most critical parts that are shared can now be accessed only by one thread. This should improve stability and reduce double free errors that make the miner crash.

With version 0.21, titan xp works flawlessly : 24500 s/s.
Cpu load is now low (rounded to 0 for my xeon 18 cores : less than with any other previous version). In my pc, there is a vega mining cryptonigth and 17 cores of the xeon mining a cpu algo coin.

Congratulation dev!

Right now working on 0.22. That one will bring a switch to bring back the 0.13 work loop as an option. This allows all for which the old version works better to switch to newer version and to profit from the other fixes.


I can not recommend doing this on CPU. Because if you use the CPU a lot the mining speed of GPU will go down. And power efficiency of CPU is much worse. Even an GTX 1030 does more sol/s then any CPU I know (well maybe except for 16+ core server CPUs ^^)


It seems we have two bugs with NVidia Windows driver here. One that makes the GPU to shut down completely (thats with zero monitor detected) and the second when there is no 3D App running lolMiner is not detected as program that requires the GPU to stay on 3D clock rates. I do not know if Nvidia workstation drivers may help here... we require a deeper investigation of this.

Can you be more specific about the error? Best way is to run the miner with --list-devices to see the order of the OpenCL platforms. It should list at least two (one Nvidia CUDA, one Advances Micro Devices... ). Maybe even three if you have an Intel IGPU installed. Then best run two instances of the miner, one for the single GTX 1050ti and one for the RX cards (here all 4 can run in one instance). In the readme are some lines how to select platform and devices.

See the answer right above. With --device and --platform you can control the OpenCL driver which cards to use.


Can not guaranty that Fury will be fastest in future versions, but I did not forget AMD for sure. 0.3 or 0.4 will come with performance tweaks, lets see how much I can do

Still it is not perfectly bug free, but definitely a large step forwards. Will see if I can do better next versions

After 24 hours all four Nvidia rigs stable on Linux, Windows 7, and Windows 10. Great job with .21!!
 

don't forget AMD R9 Fury is top hashrate on OptiminerEquihash.

I hope you develop lolminer is the same top hashrate for Fury 

plz help with bat file
lolMiner-mnx.exe --server eu.minexpool.nl --port 9999 --user XETxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj9b5Q.Worker1 --pass x
when i use on pc with 1 card work good
when i set this on rigs miner use cpu for mining not gpu ?

I would like to thanks the dev for this miner, But I need your help, not luck running this mining on my rig, here's mine

OS: WIndows 10 64x
Procie: A10 9700
Ram: 4gb

Card: 1x GTX 1050ti
         4x RX 480 8gb

I have no clue how to run it all, I made my experiment on bat file but the miner got some error..

@Lolliedeb can you please give a sample .bat config for this setup?


Thanks

connected monitor, monitor emulator does not help!!

Windows users try to install the program "Radmin". Might solve the problem with hasraton due to the device emulation video.

the same lolminer problem when running via TeamViewer hashrate 10k/SOL and more when disabled the speed drops to 5k / sol with each card . solve the problem?  4 cards 1060 6Gb

In v0.21 CPU load only 20%. Is the nv-hotfix already embedded in the miner? If yes, can it be worth making this an option? There is a suspicion that on weak processors a 20% limit will slow the hashrate. System - Ubuntu 16.04

Hi there,

This miner is really great for nvidia owners

I would just suggest a kind of watchdog in case the hashrate falls to 0 sol so the miner restarts on its own ?

Is this miner id for dual both cpu and gpu? I just want to try your mining in some of my rig,

v0.13, my bad.

this is my current batch, I've tried "WORKB" with 1,2,3,4,5,8,12, all max -20% of v0.13. Also tried using the v0.21 for one card, same result. This batch is from the last test on one card:

Rem Insert your pool name here
set "POOL=mnx.suprnova.cc"               
Rem Insert your pool port here
set "PORT=7077"
Rem Insert your user and worker names here                  
set "USER=xxxxx"     
Rem Insert your worker password here
set "PASS=xxxxxx"   

Rem Insert the index of the platform you want to run on. Run lolMiner-mnx.exe --list-devices
Rem to see all available platforms and the available devices for each platform
set "PLATFORM=1"   
Rem Insert your devices to run the miner here. For multiple GPU pass a comma separated list, e.g.: 0,1 for using two GPUs             
set "DEVICE=0"
Rem Set the work-batch-size (see readme file)
set "WORKB=3"

The batch for the v0.13 is this:

lolMiner-mnx.exe --server mnx.suprnova.cc --port 7077 --user xxxxx -- pass xxxxx --platform 1 --enable-nv-hotfix

works fine on 18khash per card apart from the occasional shutdowns of the miner.

edit: I don't think it is related, but my onboard graphics (intel) is platform 0 and is used as primary. MB is 110 Pro BTC+

7xGTX1050ti, ubuntu 16.04, G3900
6xGTX1050ti, ubuntu 16.04, AMD Athlon II
5XGTX1050, ubuntu 16.04, AMD Athlon II
4xGTX1060, ubuntu 16.04, AMD Athlon II

Uptime 12 hours.

Powerful more than v0.20

Thanks, good job!

v0.15 never existed
Can you show us your current batch for starting 0.21? Lets have a look if I see something that vould cause problems. Also you coult try running it without batch the old 0.1x way with just one card per miner instance. Lets hunt that issue

Hi, I was using v0.15 with two GTX 1080 TI and then tried to switch to v0.20 and v0.21. I played with the batch a little but I never got more than 80% of the hashrate of the v0.15. Hope this gets better (again). Good work so far 

Well, I ordered a few dummy plugs just in case... Thanks for your hard work!

Unfortunately not... especially 0.2 is just multiple copies of 0.13 thread handling in one app... as said before I may include some kind of compatiblity mode but still can not explain the difference here.