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

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 )



  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

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

What we can expect from 0.4? 

Sorry mate, seemed a great idea at the time.  

I noticed problem on a few rigs, which are not at the same location (or ISP). I use a plain config file with only pool (mnx.suprnova.cc), port (7077), and my login credentials changed. I will copy and paste log the next time it happens, but the last time it was ordinary, just showing correctly hash (all 5 cards working) but no submitting or accepted shares, just the hashes. Worker goes off the pool, and the only thing i do is just closing the miner and restarting it again, and it works like a charm, worker reappears and everyting is ok. I will post it next time it happens, but it looks plain, like this...

[Device 0] Average speed (5s): 8228.88 sol/s
[Device 1] Average speed (5s): 8544.64 sol/s
[Device 2] Average speed (5s): 8699.02 sol/s
[Device 3] Average speed (5s): 8528.66 sol/s
[Device 4] Average speed (5s): 8620.33 sol/s
[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
[Device 0] Average speed (5s): 8521.1 sol/s
[Device 1] Average speed (5s): 8533.89 sol/s
[Device 2] Average speed (5s): 8554.89 sol/s
[Device 3] Average speed (5s): 8435.51 sol/s
[Device 4] Average speed (5s): 8528.69 sol/s

Maybe I should try --max-connection-attempts command set to 5 or something like this, as I'm using plain config file with only login credentials changed?

  

Кoлoбoк, пoчeмy нa кapтax тaк cильнo oтличaeтcя paзгoн. Cдeлaй oдинaкoвым и пocмoтpи

Hello!

Do we have a restart option for the miner? I get error once a day, it stops the miner.

And did someone get all of the GPU working on the same hashes?

Not helped to me. Thank's

Thank you.

Will try with CPU.

Sory for stupid question, but what is nv-smi? If you mean temperatures - it's <60C.

I have seen this only twice yet  - on Ubuntu systems - but could be the same reasons. Can you have a look how much your system load is? It seems this happens when the miner does not get enough CPU time to load all cards with their task all of the time. One solution could be to manually set the priority of the miner to "higher" - this solved it for the one guy.

The second case was in my own testing system - a 1080 starting at 19k sol and then after some time dropping to 14.5k while the 2nd card still working at high rate. Here the slower card went so hot that it was thermal throttling. Open the case and allowing higher fan speed solved this. Whats the output of nv-smi when your cards are running?

)))
Paзгoн paзньiй.
нa oднoм pигe
+100 core
+800 memory

нa дpyгoм
+70 core
+500 memory

эx, Кoлoбoк я тeбя cъeм 
Кaкиe нacтpoйки paзгoнa видeoкapт?

Hi!
I have 2 fourcards rigs with same problem - 2 GPU's hashrate mutch lower than others 2.

[Device 0] Average speed (5s): 12551.9 sol/s
[Device 1] Average speed (5s): 7562.11 sol/s
[Device 2] Average speed (5s): 7417.15 sol/s
[Device 3] Average speed (5s): 12431.9 sol/s

Risers - OK, PSU's - OK.
Motherboards - Gigabyte ga-970a-ds3p fx.
GPU's - MSI GTX 1060 Gaming 3GB.

My command file:
@echo off
:loop
lolMiner-mnx.exe --set-work-batch HIGH --optim OFF --server eu.minexpool.nl --port 9999 --user XaJFV5fhdLURqMiASZmKDzbHcKDDPNs5jb.Gaming --pass x  
goto :loop

Can anybody help me?
Thanks a lot.

At the moment this won't work, but for the next version it will likely be. For work batch I can guaranty it, with optim I am not sure because I will do some rework of the OpenCL code and therefore the exact way optim will work is not yet fixed


As you may have read in the previous page: There is no limit by lolMiner. It can use all cards it gets reported by the OpenCL drivers without any internal restriction, therefore there is nothing I can fix.
When running Windows you must have recent Windows 10 version and recent GPU drivers. Additionally if you have AMD GPUs it seems that the blockchain drivers have problems with more then 8 GPUs. On the regular AMD Crimson drivers you still have to set the GPU profile to "Compute", here is a manual how it is done:

http://www.aurelp.com/2017/11/01/solved-how-to-add-more-than-8-gpus-in-windows-10-step-by-stepfix/



Why so bold?  No need to highlight your text that way - I am reading every post here! Can you send me the console log of your miner when this happens? Usually when the connection does down I should be able to see something in this logs. Also miner should reconnect or something like this when a share is send but it doesn't get an answer from pool. So either something is broken on pool side or one of my many safety mechanisms is not working properly (e.g. Reconnect to pool when no new job for 10 minutes, reconnect when no response to send share for 10 seconds, miner should stop sending work to GPU when there is no connection on the user connector (when fee one is broken it should get slower but not stop working) ... ) You see there are certain things that should prevent this, but I can not say why this does not work, so your config file and the text log of the miner in such a situation would be great so I can hunt down this bug.

What pool did you use to mine minexcoin? Mine is stable with 4gpu's i remove the other gpu in shift to eth algo, I hope the 8gpu limit will resolve soon by the @Dev

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).

It is a wonderful commission.

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

What's the mining fee going to be after May 1, 2018? If it's 0.5% or less, then I'd definitely try out your pool.

As always great work Mr. Lolliedieb! I will definitely going to try the latest version and let see if this version solve the 8gpu limit, once again, thanks a bunch!

What version of driver did you use mate? mine is 17.12.2 did you use the latest version of v.32? kindly need your reply. Thanks

Lolliedieb,hi. I have a question for you. Is it possible to make the --optim and --set-work-batch parameter set for each video card separately? This is necessary if there are different video cards.