[ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22)

[elektrofusion7]

What we can expect from 0.4? 

[ouray]

The newest version 0.32beta has a problem staying connected to pool. After a few hours (totaly random) miner continues hashing (and spending electricity) but worker is not connected to the pool (not mining for me).

This is a problem on a pool side not v0.32.

[Lolliedieb]

...
[Device 0] Average speed (5s): 8374.28 sol/s
[Device 1] Average speed (5s): 8435.19 sol/s
[Device 2] Average speed (5s): 8431 sol/s
[Device 3] Average speed (5s): 8510.09 sol/s
[Device 4] Average speed (5s): 8481.73 sol/s
...  

Sorry, that snap was a bit too short To do some debugging I need to know in which state the stratum connection was and what counters were running / or were long expired at the time your connection stops working. So to get a complete picture of the situation I require the log from approx the moment where you got the last difficulty / new job adjustment (but connection was working fine till then) until you decided to stop the miner because its not sending shares. That should be long enough so I can see which of my safety timers (that should prevent this) is not working.

The --max-connection-attempts will only work if you define a failover pool and then still the miner has to detect that the connection is broken. Usually it should detect this at some time and then reconnect, but somehow it does not do so. Therefore would be great having the longer log and the config. (But plz in private message - I guess this could be a loooooong post here else )

What we can expect from 0.4? 

0.08 more than 0.32?

  Thats for sure ^^
I currently plan to do some changes in the work scheduling. I aim for making the stuff less dependent on the memory on the GPUs so the 4G cards should do same speed as the 8G (on AMD in particular), since this currently is not the case. Also I want to exclude the status message code into an external module. Currently there are only two large code fragments, one for mining and one for the connection. This will be connection, mining and logging then. Pulling out the stats code out of the mining section will allow me to do more fancy stuff with it, e.g. providing a JSON API for the miner, so you can grab statistics for external analysis.

One further point I have on my list - but do not know yet if that will be 0.4 or later is a re-design of my mining code itself. Currently AMDs are suffering from the code to eat vector registers when compiling like Candy preventing the AMD scheduler to do efficiently place work on the card and cover all latencies. The re-structuring there should also allow to introduce more switchable optimizations.

Yea, I think thats it

[ouray]

Hoping I don't bother or break a rule here.
Please help this brand new MNX pool: https://mnx.forgetop.com

The question is: how stable is your pool in term of connectivity?
I was wondering if you try to get miners in offering a FREE rate for a months or two like MinexPool.XYZ.
Anyhow, I look forward to it after get off work today.

[Lolliedieb]

Well ... there is an extra forum here where you can announce and discuss new pools - maybe setting then a link in the Minex general pool is a good idea.
But here this is getting a bit to much if I get one pool advertising per page - this is for discussing and giving support for lolMiner.

I have to announce that I just released version 0.33.

The reason is that I investigated the bug that some users claim the miner disconnecting from pool. I do not have a full log here but just by inspecting the code I found a problem that may have caused this and where the miner defiantly did not handle things like it should be. Well - I do not know if this causes the problem, but I fixed at least one issue now that I did not want to keep in code until 0.4 is done  

Link is - as usual - on the thread front page. Also I now computed the checksums of the lolMiner binaries so you can compare if files you get are integer.

[The Godfather]

did you fix miner breaking every 24h ?

[Raty]

Anyone working with mining rig 6x GTX 1080ti on Windows 10 pro??
I have 4 rigs with 1080ti and 2 rigs with 1080 .. all with 6 cards.

With 1080 it is working without any problem.
But on any my 1080ti rig it not working. After some minutes rig unexpected restarted (no BSOD dump file generated). When I set device only on 1,2,3,4,5 (except 0) it works about 20-40 minutes when it crash. With device 0 active it will crash in 2-5 minutes.
Any tips? I have new updates and new drivers too. I tried to reset OC to default (i tried set less OC then default too), set powerlimit to 80 or 90 or 100 or 110% but nothing helped.

Thanks for any help

[optiminer]

Under what license is this miner distributed?

Is the source available? It seems to use GPLed code, so I would expect it to be.

[uhro]

Under what license is this miner distributed?

Is the source available? It seems to use GPLed code, so I would expect it to be.

Do you hate Windows or something?
People have been asking you to do a Windows version of your MNX miner for 4+ months and now that there is one that's actively being developed you're questioning it...
I agree it's probably something that should be open source, but as a miner, I'm just happy someone is finally actively developing a Windows version, something you could have done months ago.

[Lolliedieb]

Under what license is this miner distributed?

Is the source available? It seems to use GPLed code, so I would expect it to be.

Hi there,
Can you be more specific which code under GPL you think I am using?  The only external libraries I use and link at the moment are the boost library and the g++/mingw64 runtimes. Well and OpenCL of cause. I hope I am not wrong here, so if you found somethink I use that I am not allowed to I will remove it immidiately.  I wrote most of this from scratch - don't even have the external equihashverify code from node code in here. Beeing a bit more specific could help clarifying this.

Anyone working with mining rig 6x GTX 1080ti on Windows 10 pro??
I have 4 rigs with 1080ti and 2 rigs with 1080 .. all with 6 cards.

With 1080 it is working without any problem.
But on any my 1080ti rig it not working. After some minutes rig unexpected restarted (no BSOD dump file generated). When I set device only on 1,2,3,4,5 (except 0) it works about 20-40 minutes when it crash. With device 0 active it will crash in 2-5 minutes.
Any tips? I have new updates and new drivers too. I tried to reset OC to default (i tried set less OC then default too), set powerlimit to 80 or 90 or 100 or 110% but nothing helped.

Thanks for any help

Sorry to hear that but a bit hard to debug from the distance. Could be too much CPU load or work batch turned toi high or well - just a runtime bug of the Windows binaries (not that unlikely - there still seem to be certain of them ) Have you tried running the rig with hiveos or any other Linux? If its crashing there too its likely that this due to system stability - if not its my shitty Windows binaries... I am a bit sirry that these are not better yet :/

[ninjam]

Anyone working with mining rig 6x GTX 1080ti on Windows 10 pro??
I have 4 rigs with 1080ti and 2 rigs with 1080 .. all with 6 cards.

With 1080 it is working without any problem.
But on any my 1080ti rig it not working. After some minutes rig unexpected restarted (no BSOD dump file generated). When I set device only on 1,2,3,4,5 (except 0) it works about 20-40 minutes when it crash. With device 0 active it will crash in 2-5 minutes.
Any tips? I have new updates and new drivers too. I tried to reset OC to default (i tried set less OC then default too), set powerlimit to 80 or 90 or 100 or 110% but nothing helped.

Thanks for any help

Does it happen to 1 of the 4 1080ti rigs or all of them? Enough power for those rigs? Unexpected reboots can be due power supply not being able to handle the load. I have mixed rig with 1060, 1070, 1080 and 1080ti and it works without restarting, sometimes there is a problem with the miner but watchdog can handle that. To me looks like that you have some hardware problem. Does it work stable with other algos?

[chup]

Does it happen to 1 of the 4 1080ti rigs or all of them? Enough power for those rigs? Unexpected reboots can be due power supply not being able to handle the load. I have mixed rig with 1060, 1070, 1080 and 1080ti and it works without restarting, sometimes there is a problem with the miner but watchdog can handle that. To me looks like that you have some hardware problem. Does it work stable with other algos?

Put the 1080tii as a first card and You will see miner and driver crashes in no time.

[ALFA-Dnepr]

GTX 1060 3Gb ver. 0.31 11300 Sol/s
GTX 1060 3Gb ver. 0.33 10200 Sol/s
??

[smoolae]

GTX 1060 3Gb ver. 0.31 11300 Sol/s
GTX 1060 3Gb ver. 0.33 10200 Sol/s
??

Silicon lottery

[Matico1]

Does any of the updates repair the crash of the miner? Otherwise I will still be using v0.31, it seems to be working good except one error ususally after 10pm..

[Mapuo]

Lolliedieb, can you do something about this?

Hey,

Seems that lolMiner don't have API, only way to use it, is with Stats only mode, you can upload it with Custom software if you want to use it right now.

Ethmonitoring is a very useful tool, and it will be nice to work with your miner.

[KuzNet]

Good news, everyone!
New mining pool for MinexCoin!
http://MinexPool.xyz
Mining fee is 0% until 01.05.2018, minimal payment is 0.1 MNX
Welcome!

Telegram Support Group: https://t.me/minexpool

It is a wonderful commission.

Can I change the number of payment?
If change is possible I will switch from Suprnova.

We're implenting this feature now. And new beautiful UI for your eye's pleasure

[john1010]

I tried the v.33 and this is the result..

I am using 4 RX 480 8gb
1 RX 570 8GB
1 RX 570 4GB

and I set the --set-work-batch HIGH : make my other cards to zero

instead I set to --set-work-batch AUTO

and I got this >>>

[Matico1]

I just noticed that one of my power supply is not working(ventilator not spinning)..When I start mining both of them starts but after some time, one stops. But the hashes are the same and it is quite hot.. Gonna try to mine something else to find out if both of them are working.

[uhro]

The --exit-on-zero option doesn't seem to be working, I just had my rig run for about half hour at 0 before I caught it...