Pages:
Author

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

newbie
Activity: 27
Merit: 0

Hello, developer. rx580 gives the optimizer 10ksol on Linux, and on your 6.5, maybe it's all about the intensity ?? Wink
full member
Activity: 271
Merit: 103
Hi pool operator of minexpool here.
Dev, plz contact me on Telegram,  @Racquemis
The introduction of your miner is causing problems on the pool which should be resolved asap.
Let's work together to fix this.
newbie
Activity: 33
Merit: 0
V 0.12 gives me full speed for my 1080's - but I can't run more than one instance of the miner.
One is stable (for 30 minutes so far), any more than that crashes the miner.

I'm just going to bring this up again.

In version 0.11, WITH the nv hot fix, I was getting full stable speeds with three instances of your miner running on my rig, ONLY when I would connect to the computer through team viewer.

Screen - SLOW
No screen - SLOW
Connect with team viewer - BOOM, FAST

This works every. Single. Time.

Cheers
newbie
Activity: 7
Merit: 0
Hello, my internet or computer seems to be so slow, that it doesn't have enough time to connect to the pool, before the program starts to spam pool with reconnections, and I get kicked out from the pool. I don't really think it should work that way? Sometimes I get connection in time, anyway, it loses usually approximetly in 1 hour and then it starts to spam that reconnect and again breaks down. Can you make it do those connection things bit more slowly. Like give it some more seconds to connect, and do it have to try to reconnect twise in second? It should really be OK to try like every 10 second?  

edit:

My Win10 computer with GTX 1080 gives this connection problem / bug and after a while whole program goes down. And in windows 7 i got another 1080 and 1050, these both dont work more than~10 seconds. After 10 seconds it just quits, with no warning at all. Picture under shows the connection bugging first on windows 7 computer, after it connects, it almost immidietly quits. With no message at all. And it does it with gtx1080 and 1050 both.

https://imgur.com/a/atk9k
full member
Activity: 271
Merit: 103
Hi Lolliedeb, check your pm. Send you a message regarding the wrong parameters 'problem'
newbie
Activity: 10
Merit: 0
So, lets go for New Version 0.12

Fix of the "compile() error"
The miner now also runs on older AMD implementations with the official AMD drivers. The most ancient card I tried was a Radeon HD 7770 (GCN 1, released February 2012 (!) ) and it runs fine with about 600 sol/s when using Windows 10.


Thank you!!! this worked for me, but hash rate still lower than on optiminer for RX560 2500 vs 5000H/s
member
Activity: 433
Merit: 48
So, lets go for New Version 0.12

As usual here are die Download links:
Linux 64: Click Here
Windows 64: Click Here

Change log:

Changes to the "--enable-nv-hotfix" switch
The hotfix is now a bit less aggressive compared to v 0.11. It may be that the CPU load is slightly up compared to the previous version, but the new algorithm is doing better when recovering from a time with overall high CPU load. If the old version worked better at your side you can still download the old version v0.11 here (Win 64) and here (Lin 64) .

In general for the miner monitor the load during the first minutes of running. If you have an overall system load above 60% I would recoment running less instances of lolMiner and use the remaining graphic cards for mining with an other coin.

Fix of the "compile() error"
The miner now also runs on older AMD implementations with the official AMD drivers. The most ancient card I tried was a Radeon HD 7770 (GCN 1, released February 2012 (!) ) and it runs fine with about 600 sol/s when using Windows 10.

Fix of a "lucky user" bug.
There was one strange bug in the miner causing a segfault when too many solutions were found with one equihash run. Usually on average about 2 solutions are found, 4-5 can happen, but I had one report of 10 solutions in one run. v 0.11 was not prepared for this, but now it is ^^

Improvements to reconnect function.
Before there were multiple threads testing if the stratum connection is still valid and that may have issued a reconnect. This sometimes caused that thread #1 wanted to restart the reconnect attempt just started by thread #0. Now there is exactly one thread left that is able to issue a reconnect when an error is detected. Also after the first reconnection attempt the miner will now wait for 30 seconds to give the pool time to respond before the next reconnection attempt is taken.

Shipment with new libraries in Windows version
We had some reports about libstdc++ library crashes in Windows version. I updated all libraries in Windows version to newer versions. This does not guaranty that the stability issues are gone, but maybe the new versions help. At least I had no issues with the new versions in first testing.


New known issues:
Connection reseted by peer (Linux),  A connection was disconnected by the software on the host computer (Windows), Received job has wrong number of parameters! (both), All on minexpool.nl
I do not know yet why - either if this is a pool issue over the last two days or if this is an issue of the miner. At least the miner had some trouble connecting to the pool sometimes and receives irregular messages from this pool from time to time. The connection reseted by peer message often seems to affect the miner when no share was send in more than 90 seconds. Future will show if this is miner or pool bug and if there are efficient countermeasures to handle this. Currently I can observe that the miner is able to recover from the issue by reconnection, but of cause this lowers income when shares get lost and the miner is waiting for a reconnection attempt.  

Adding something like --retries and --retry-delay would be nice or even backup pool options.
If you just allowed the program to exit after failing to reconnect the specified amount of --retries consecutively, it would allow us to simply run a new instance trying another pool automatically.

I will definitely consider this as one possible feature for next release version. Good idea Smiley


----------
Current hash-rate of all lolMiners out there: ~1.9 to 2 Msol/s
Market share: ~3.5%



full member
Activity: 132
Merit: 100
@ Syth:

Currently the miner tries to re-connect too often when it things that connection is lost. Next version will reduce the number of attempts and also give the connection more time for recovering.

From my experiments with my 24 hours run the earnings were accurate (on Optiminer pool) according to the pool luck. On minexpool I did not test but I know that difficulty is higher there, so on the long term the earnings should fit, but it can be more volatile on the short term. As always it is important that the average sol/s detected by pool (over one hour or more) fit to whan the miner displays on command line. Then the miner works well. Everything else is in the responsibility of the pool.
Adding something like --retries and --retry-delay would be nice or even backup pool options.
If you just allowed the program to exit after failing to reconnect the specified amount of --retries consecutively, it would allow us to simply run a new instance trying another pool automatically.
member
Activity: 433
Merit: 48
@ Syth:

Currently the miner tries to re-connect too often when it things that connection is lost. Next version will reduce the number of attempts and also give the connection more time for recovering.

From my experiments with my 24 hours run the earnings were accurate (on Optiminer pool) according to the pool luck. On minexpool I did not test but I know that difficulty is higher there, so on the long term the earnings should fit, but it can be more volatile on the short term. As always it is important that the average sol/s detected by pool (over one hour or more) fit to whan the miner displays on command line. Then the miner works well. Everything else is in the responsibility of the pool.
full member
Activity: 132
Merit: 100
After mining for over 24 hours split evenly on the two pools I have mined under 0.1 MNX on each pool. (12 hours on each)
That's 0.18 MNX after 24+ hours of mining using 10KSol/s.
I know the pool stats aren't always that accurate but it should give an estimate of how many coins you would mine given the current difficulty.
When I started mining the pool reported 1.9 MNX/day, was down to ~1.5 at some point and now at ~1.8/day.

Are the pool stats way off or is there something I am not seeing here?


Also not sure if these issues are unreported:

I think I only get this one on the eu.minexpool.nl pool:
Code:
Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer

Reconnecting in 500ms
Connected!
Subscribed to stratum server
New target received: 0000555555555555540000000000000000000000000000000000000000000000
Warning: Received job has wrong number of parameters!
9

And this is I think is coming at times of bad internet connection, so maybe not an issue with the miner:
Code:
Warning: Incomplete response
Submitting share
Average speed (5s): 9618.18 Sol/s
Average speed (5s): 9672.6 Sol/s
Warning: too long between share and accept. Trying to reconnect.
Reconnecting in 500ms
Connecting to stratum server eu.minexpool.nl:3333
Average speed (5s): Warning: read_until: A connection was disconnected by the software on the host computer
Warning: read_until: A connection was disconnected by the software on the host computer

Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer
Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer
Warning: read_until: A connection was disconnected by the software on the host computer
full member
Activity: 132
Merit: 100
Not worthless at all: you can use a shell script for an automatic relaunch:
 in a .bat:

echo -------------------------------------------------------------------
echo Simple script to restart your miner software after a period of time
echo -------------------------------------------------------------------
echo:

set executable=lolMiner-mnx.exe
set commandline= --server mnx.suprnova.cc --port 7076 --user xxxxx  --pass x    --platform 1
set /a counter=0
:start
%executable% %commandline%
echo:
echo Restarting the software  (%counter%)
set /a counter+=1
echo:
echo:
goto start
Did you test this script for hours mining?
If you look back in this thread you'll see a different script that I posted.

At first I ran lolMiner directly from the batch file like yours does and seemed to work fine, restarting when miner stopped.
The issue I had was after ~6 hours of run time the cmd window of the batch running the miner crashed or simply closed completely.
That's why I changed the script to open a new cmd process with the miner running inside instead. restarting this cmd instead aswell.

Although the script that I posted is for multiple GPUs, this was not for me and I am only running a single card.
sr. member
Activity: 896
Merit: 289
Twitter: @BTY_11073
Oh, this miner is a wonderful performance!
I hope that stability improves and Dev fee goes down.

Thank you, Lolliedieb. Good job. Cheesy
member
Activity: 433
Merit: 48
I have similar behaviour on a titan xp. Far worse performance with --enable-nv-hotfix.

System : windows 10 (creator update)
cpu : xeon E5 2696V3 (18 cores @3.2ghz with microcode/bios hack).
With the hotfix enables, performance is aroung 5 instead of 22-23. Cpu usage is very low ( less thant 20% for a dedicated core). Without the hotfix, performance is good and cpu usage is near a full dedicated core.

Would you allow me to send you a private message? Unfortunately the forum still indicates me as being a newbie and your settings currently does not allow me to send a message.
jr. member
Activity: 192
Merit: 5


What about Laptop mining? specs I5 7th gen processor , Nvidea Geforce 940Mx VGA.. is this specs enough to mine some XMR?
[/quote]

This miner is for Minexcoin (MNX).
newbie
Activity: 209
Merit: 0
sr. member
Activity: 445
Merit: 255
The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols

Hi out there. I wanted to write a private message to you but I am not allowed to - may you contact me via PM how to get in contact about this?
Thanks



Else: Is there anyone out there having problems with the NV hotfix that is causes hash-rate to drop too much (on Nvidia of cause ... enabling this with Intel or AMD will likely kill your hashrate) and that is online right now?

If I get the new hotfix tested it is likely we will have an other release later today (I did not plan to do v 0.12, but fixed enough stuff to make it worth not to wait until v 0.2 which will come with new feats somewhere next days).

Yes. Cf my post on page 5
On windows 10 x64 (without --enable-nv-hotfix)
1x1070 - 14.0-15.0
2x1070 - 10.0-10.5
3x1070 - 7.8-8.2
1x1050 - 5.0-5.2

On windows 10 x64 (with --enable-nv-hotfix)
1x1070 - 1.8-3.0
2x1070 - 1.8-3.0
3x1070 - 1.8-3.0
1x1050 - 5.0-5.2

On ubuntu 16.04 (with --enable-nv-hotfix)
3x1070 - 13.2-14.0 (core 150, mem 300)
4x1060 - 8.7-9.2 (core 100, mem 200)
5x1050ti - 5.3-5.8 (core 50, mem 0)


Best solution for linux, more hashes than optiminer
Uptime on linux 8 hours

I have similar behaviour on a titan xp. Far worse performance with --enable-nv-hotfix.

System : windows 10 (creator update)
cpu : xeon E5 2696V3 (18 cores @3.2ghz with microcode/bios hack).
With the hotfix enables, performance is aroung 5 instead of 22-23. Cpu usage is very low ( less thant 20% for a dedicated core). Without the hotfix, performance is good and cpu usage is near a full dedicated core.
hero member
Activity: 610
Merit: 500
  Имя coбытия пpoблeмы:   APPCRASH
  Имя пpилoжeния:   lolMiner-mnx.exe
  Bepcия пpилoжeния:   0.0.0.0
  Oтмeткa вpeмeни пpилoжeния:   5a82e1bf
  Имя мoдyля c oшибкoй:   libstdc++-6.dll
  Bepcия мoдyля c oшибкoй:   0.0.0.0
  Oтмeткa вpeмeни мoдyля c oшибкoй:   56be6eb2
  Кoд иcключeния:   c0000005
  Cмeщeниe иcключeния:   00000000000c66b6
  Bepcия OC:   6.1.7601.2.1.0.256.1
  Кoд языкa:   1049
  Дoпoлнитeльныe cвeдeния 1:   a637
  Дoпoлнитeльныe cвeдeния 2:   a6376028ded939d5a943c3d8429c4ac2
  Дoпoлнитeльныe cвeдeния 3:   ee42
  Дoпoлнитeльныe cвeдeния 4:   ee42532b49ea6cebba1f2ad6d0011676 win 7 64 bit 1080 driver 384
member
Activity: 433
Merit: 48
The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols

Hi out there. I wanted to write a private message to you but I am not allowed to - may you contact me via PM how to get in contact about this?
Thanks



Else: Is there anyone out there having problems with the NV hotfix that is causes hash-rate to drop too much (on Nvidia of cause ... enabling this with Intel or AMD will likely kill your hashrate) and that is online right now?

If I get the new hotfix tested it is likely we will have an other release later today (I did not plan to do v 0.12, but fixed enough stuff to make it worth not to wait until v 0.2 which will come with new feats somewhere next days).
newbie
Activity: 33
Merit: 0
Running fairly stable here on W10, except that when I shut off teamviewer, hash rate drops from 14ksols to 1500 sols...
Then jumps right back up when team viewer is turned on again.

Ideas?  Huh

TeamViewer generally eats graphic power, see here:
https://www.reddit.com/r/gpumining/comments/7mwgpc/high_gpu_usage_in_teamviewer_pc_mining/

@All that habe problems with the --enable-nv-hotfix:
It seems that on some systems the current version is to aggressive. I will try an alternative variant in the next hours and hopefully find a solution that works for all users. If new one looks more promising, will be included in the next version.





No sir, the other way around.
When I turn on team viewer, hash rate goes UP (1500 -> 14000)
When I turn the remote display (TV) OFF, hash rate goes DOWN.

Weird, huh?

This is both on the miner and poolside, btw. Like clockwork.

Added - Im also testing on 2x 1080s and one 980ti for now.
Would rather not linux this one.
member
Activity: 295
Merit: 10
I'm testing with RX 460 4GB. Successful Wink

Pages:
Jump to: